New answers tagged claims-based-auth
Check this link. They had explained how to hide the default Multiple authentication provider page. http://msdn.microsoft.com/en-us/library/office/hh237665(v=office.14).aspx
I believe I have solved my issue. Half of the issue was also stemming from stale PowerShell sessions, for example I'd leave my PowerShell window open during changes to my Claims Provider but changes were never reflected until I started a new PowerShell session. This is the reason why my EnsureUser was actually showing that it was working even when it ...
I would recommend JShare. It is Android and Java library for SharePoint. It supports few authentication options including NTLM.
On the SharePoint side, no. In a Provider-hosted app, it is the responsibility of the remote web to authenticate the user and pass that identity to SharePoint as part of the token. If you have trusted the app to make app-only calls, then you have to trust the app. :)
Refer the below link which explains how to override the people picker to provide the valid values. http://blogs.msdn.com/b/kaevans/archive/2013/05/26/fixing-people-picker-for-saml-claims-users-using-ldap.aspx
try the below code and see if it works $claim = New-SPClaimsPrincipal -TrustedIdentityTokenIssuerr $ap -Identity UserName $site = New-SPSite $url -OwnerAlias $claim.ToEncodedString() -template "STS#0" I think you need to encode the string to get it works. http://technet.microsoft.com/en-us/library/ff607753(v=office.14).aspx#section1 Also check this one: ...
Yes. I'm going to assume that you have a proscribed set of permission that should be assigned to certain users. First work out what your default users should have access to in terms of view/edit/manage etc. for each part of the site. Next either create a new user group or use the Members group. As a general rule you'll likely have a view permission for ...
At the end of you code it looks like your code is using the same method to impersonate as in a classic auth app with integrated auth. This is not working in a claims app because the used authenticated using kerberos in the initial handshake (url: _trust/...). The claims to windows token service is not doing the magic automatically. You have to request a ...
Top 50 recent answers are included