Renew SP SSO certificate

http://www.benjaminathawes.com/2013/07/31/how-to-renew-your-adfs-2-0-token-signing-certificate-in-sharepoint/

# Find the ADFS token signing cert$cert= New-Object System.Security.Cryptography.X509Certificates.X509Certificate2(“C:ADFSTokenSigning.cer“)# import cert to trusted root authority store in SharePointNew-SPTrustedRootAuthority -Name “ADFS Token Signing” -Certificate $cert# import cert to SP-TrustedIdentityTokenIssuerget-SPTrustedIdentityTokenIssuer | Set-SPTrustedIdentityTokenIssuer -importtrustcertificate $cert
Renew SP SSO certificate

Crack windows password

crack win passw

http://security.stackexchange.com/questions/63890/does-windows-have-a-built-in-password-store

=>

http://www.tarasco.org/security/pwdump_7/

http://www.ampliasecurity.com/research/wcefaq.html

http://www.l0phtcrack.com/help/using.html
read

http://www.windowsecurity.com/articles-tutorials/authentication_and_encryption/How-Cracked-Windows-Password-Part1.html

http://www.windowsecurity.com/articles-tutorials/authentication_and_encryption/How-Cracked-Windows-Password-Part2.html
http://bernardodamele.blogspot.ru/2011/12/dump-windows-password-hashes_16.html

Crack windows password

sharepoint error dispaly

web.config

C:\inetpub\wwwroot\wss\VirtualDirectories\443

<compilation batch=”false” debug=”true”> (debug was false)

<SafeMode MaxControls=”200″ CallStack=”true” DirectFileDependencies=”10″ TotalFileDependencies=”250″

AllowPageLevelTrace=”false”> (callstack was false)

<customErrors mode=”Off” /> (was On)

C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\LAYOUTS

<customErrors mode=”Off” /> (was On)

sharepoint error dispaly

post

have sharepoint 2010 with ADFS. I also created custom claims provider and set it’s name as ClaimProviderName property of SPTrustedIdentityTokenIssuer for ADFS. But now I’d like the default ADFS people picker back again. But when I try to set ClaimProviderName to empty string, I’m getting error that claim provider does not exist. I tried empty string, $null, but nothing seems to work.

 

here is no way to change the claimprovider back to the original one. You’ll have to remove the SPTrustedIdentityTokenIssuer and create it again with the right settings. Be sure to use the same name if you want your existing users to be able to login again.

  1. Remove your SPTrustedIdentityTokenIssuer from all web applications
  2. Delete your SPTrustedIdentityTokenIssuer
  3. Create a new SPTrustedIdentityTokenIssuer with the same settings as before (but without the settings you’re trying to remove)
  4. Configure your web applications to use the SPTrustedIdentityTokenIssuer again
post