saml-2.0

问题 I need to get HttpContext.Session in GrantResourceOwnerCredentials method. However I get null when I try to access Httpcontext.Session . Below is my code: public void ConfigureAuth(IAppBuilder app) { PublicClientId = "self"; OAuthOptions = new OAuthAuthorizationServerOptions { TokenEndpointPath = new PathString("/Token"), Provider = new ApplicationOAuthProvider( PublicClientId, DependencyResolver.Current.GetService<ApplicationUserManager>(), HttpContext.Current), //AuthorizeEndpointPath = new

问题 I'm trying to dynamically add a SAML2 authentication scheme using IAuthenticationSchemeProvider in ASP.NET Core and the Sustainsys.Saml2 library: schemeProvider.AddScheme(new AuthenticationScheme("myAuthScheme", "myAuthScheme", typeof(Saml2Handler))); Along with the scheme, I need to configure the Saml2Options that go along with it. I'm attempting to do this using IOptionsMonitorCache<Saml2Options> like so: samlOptionsCache.TryAdd("myAuthScheme", options); When I then attempt to authenticate

问题 I have only one JDK installed in my machine and the code is pointing to the same JDK. I have installed unlimited strength cryptography library in both the folders(C:\Program Files\Java\jdk1.6.0_25\jre\lib\security and C:\Program Files\Java\jre6\lib\security). I keep getting the same exception even after adding the above mentioned unlimited strength library. This is in continuation to other ticket link Exception: Caused by: java.security.InvalidKeyException: Key is too long for unwrapping at

问题 I have been trying to add a "virtual" claim provider (SAML 2.0 Identity Provider) in ADFS, I have another claim provider with same certicate. I get this error on ADFS2.0 in windows Server 2012 MSIS7600 Each Signing Certificate value for a claims provider Trust must be unique across all claims provider trusts in ADFS 2.0 configuration Is there any workaround to avoid this issue? 回答1: No, I got the same thing here. Appearantly it must be unique. I tried to add 2 tenants (2 customers) coming

问题 I have been trying to add a "virtual" claim provider (SAML 2.0 Identity Provider) in ADFS, I have another claim provider with same certicate. I get this error on ADFS2.0 in windows Server 2012 MSIS7600 Each Signing Certificate value for a claims provider Trust must be unique across all claims provider trusts in ADFS 2.0 configuration Is there any workaround to avoid this issue? 回答1: No, I got the same thing here. Appearantly it must be unique. I tried to add 2 tenants (2 customers) coming

问题 I'm trying to implement WSO2 Single Logout functionality in my java webapp. And I cannot understand this thing: I set SAML Single Logout option for 2 my Issuers. Then I call logout for first Service Provider (SP), IdP redirects it to some logout url with SAML Response, SP gets this request and invalidates http session. Second SP also gets request from IdP with SAML Response, but http session in this request is a session between IdP and SP, and I need to invalidate session between web browser

问题 I have succesfully configured SSO using WSO2IS 4.6.0 and spring saml grails plugin, but when I enable signing and signature validation like this: I see errors on WSO2 console WARN {org.wso2.carbon.identity.sso.saml.util.SAMLSSOUtil} - Signature Validation Failed for the SAML Assertion : Signature is invalid. DEBUG org.wso2.carbon.identity.sso.saml.util.SAMLSSOUtil} - org.opensaml.xml.validation.ValidationException: Unable to evaluate key against signature WARN {org.wso2.carbon.identity.sso

问题 Hey I am trying to configure IDP with my service provider but when saml response comes from IDP I got this error in my service provider org.opensaml.common.SAMLException: NameID element must be present as part of the Subject in the Response message, please enable it in the IDP configuration at org.springframework.security.saml.websso.WebSSOProfileConsumerImpl.processAuthenticationResponse I configured NameId in idp - metadata xml <NameID>urn:oasis:names:tc:SAML:1.1:nameid-format

问题 I am new to SSO as well as Shibboleth. I have successfully implemented Shibboleth SP on an Apache Server. The user is getting authenticated against IDP whenever the user tries to access a protected resource. Basically, Shibboleth SSO has the following 6 steps: User Accesses Protected Resource SP Determines IdP and Issues Authentication Request User Authenticates to the IdP IdP Issues Response to SP Back to the SP Back to the Protected Resource My client app is purely developed using AngularJS

问题 I am having quite a time setting up SAML integration with a client using our platform. We're using OneLogin's php sdk on our end to act as a service provider. Not sure what they're using as an identity provider or if it is something custom. It seems no matter what we do, the AuthN Response we receive from them has the status: urn:oasis:names:tc:SAML:2.0:status:Responder As I read it here, all that means is that there was an issue (we don't know what) on their side. Sort of the equivalent of a