spring-saml

SAML remote Discovery service : missing “return” parameter

偶尔善良 提交于 2019-12-24 12:35:13
问题 I'm using Spring Security SAML 1.0.1. I've set up the IDP metadata so it reaches a Discovery service which is defined by idpDiscoveryURL . This parameter contains the URL http://wayf-shib.ueb.eu/fede-renater/WAYF . The remote Discovery is reached, but it complains that the request does not contain the "return" parameter. Indeed, this is the request that Spring SAML generates: http://wayf-shib.ueb.eu/fede-renater/WAYF?entityID=http%3A%2F%2Facem.u-bretagneloire.fr%3A80%2FACEM%2Fsaml%2Fmetadata

Spring Security SAML IdP Metadata Certificate and Signature

空扰寡人 提交于 2019-12-24 05:15:13
问题 I have looked at many questions including https://stackoverflow.com/a/25384924/1317559. I have the IdP metadata and certificate, but can't seem to get Spring so see it. Added the certificate to the keystore: keytool -importcert -alias adfssigning -keystore samlKeystore.jks -file certificate.crt In the metadata there are multiple certificates (2 different ones) and a SignatureValue. I tried to add the signature value with the same keytool command, but it is not a certificate. I tried to add

Spring saml: Key is too long for unwrapping: invalidkeyexception

假如想象 提交于 2019-12-24 05:13:29
问题 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

SSO with signing and signature validation doesn't work

♀尐吖头ヾ 提交于 2019-12-24 01:08:34
问题 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

NameID element must be present as part of the Subject

让人想犯罪 __ 提交于 2019-12-24 01:05:22
问题 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

Spring SAML handshake failure - Failed to validate untrusted credential against trusted key

天大地大妈咪最大 提交于 2019-12-22 13:56:34
问题 I'm using Spring Security SAML extension for integrating with the ACA healthcare (aka Obamacare) website. It uses IDP Initiated SSO. The SAML handshake fails with the following output org.opensaml.xml.security.keyinfo.provider.InlineX509DataProvider] Single certificate was present, treating as end-entity certificate org.opensaml.xml.security.keyinfo.BasicProviderKeyInfoCredentialResolver] Credentials successfully extracted from child {http://www.w3.org/2000/09/xmldsig#}X509Data by provider

SAML service provider spring security

两盒软妹~` 提交于 2019-12-22 06:12:23
问题 When using pre-configured service provider metadata, in spring security, should there be 2 beans definitions for extended metadata delegate ? one for IDP metadata, and one for SP metadata ? <bean class="org.springframework.security.saml.metadata.ExtendedMetadataDelegate"> <constructor-arg> <bean class="org.opensaml.saml2.metadata.provider.FilesystemMetadataProvider"> <constructor-arg> <value type="java.io.File">classpath:security/localhost_sp.xml</value> </constructor-arg> <property name=

SAML service provider spring security

人走茶凉 提交于 2019-12-22 06:10:52
问题 When using pre-configured service provider metadata, in spring security, should there be 2 beans definitions for extended metadata delegate ? one for IDP metadata, and one for SP metadata ? <bean class="org.springframework.security.saml.metadata.ExtendedMetadataDelegate"> <constructor-arg> <bean class="org.opensaml.saml2.metadata.provider.FilesystemMetadataProvider"> <constructor-arg> <value type="java.io.File">classpath:security/localhost_sp.xml</value> </constructor-arg> <property name=

SAML service provider spring security

感情迁移 提交于 2019-12-22 06:10:00
问题 When using pre-configured service provider metadata, in spring security, should there be 2 beans definitions for extended metadata delegate ? one for IDP metadata, and one for SP metadata ? <bean class="org.springframework.security.saml.metadata.ExtendedMetadataDelegate"> <constructor-arg> <bean class="org.opensaml.saml2.metadata.provider.FilesystemMetadataProvider"> <constructor-arg> <value type="java.io.File">classpath:security/localhost_sp.xml</value> </constructor-arg> <property name=

Spring-SAML : Incoming SAML message is invalid

*爱你&永不变心* 提交于 2019-12-21 16:53:31
问题 I am facing an issue while integrating my app with SAML. The following is my error: org.springframework.security.saml.SAMLProcessingFilter.attemptAuthentication: Incoming SAML message is invalid org.opensaml.common.SAMLException: Endpoint with message binding urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST and URL https://myappruldotom/saml/SSO wasn't found in local metadata at org.springframework.security.saml.util.SAMLUtil.getEndpoint(SAMLUtil.java:357) ~[spring-security-saml2-core-1.0.2