New answers tagged claims-based-auth
Bear with me as I'm more SharePoint admin than PING expert but I've had to work on a similar solution for our organisation (allbeit incomplete). For our SharePoint 2013 implimentation, we are aligning with the organisation's SSO using PING Federate. However, we typically control access to SharePoint site collections etc via AD groups. We were able to get ...
What you are looking for is possible but will require quite some work and deep knowledge about kerberos. Reverse proxy solutions like Microsoft TMG are doing what you would like to do. It is possible to implement "some kind" of reverse proxy that will take the username and password from an ASPX page, store the data in "some" place and use the reverse proxy ...
Can you try out claims/kerberos? Neither classic/ntlm nor claims/ntlm supports delegation. Potentially this is causing the access denied. Also check out this post: Is Classic/NTLM based authentication a security riskfor Internet facing sites?
As @BennySkogberg mentioned, you need to specify a UPN explicitly for the users you want to change. You will probably want to setup the Forest or Organisational Unit (tenanted) with a UPN Suffix. Once you have set the suffix, you should be able to select it under the user's Account name. You can use ADSI Edit to modify the uPN Suffix property, or use ...
It was working fine until I changed the default zone's authentication method to allow FBA in addition to Win Auth (claims). Instead of changing the default zone, I think you should have extended the web application. If you can't switch things back to how they where, I would consider to restore the web application: Considerations when restoring a Web ...
You should have the option to select the Display Name or User Name(among other options)
Top 50 recent answers are included