Apparent inconsistencies in the Shibboleth wiki concerning persistent NameIDs for federating a Shibboleth IDP with Microsoft Azure

[Michael A Grady]

Forgot to add the definition of SHA1SecurityConfig, which I had just before the Overrides section of relying-party.xml
---

	<bean id="SHA1SecurityConfig" parent="shibboleth.DefaultSecurityConfiguration"
	   p:signatureSigningConfiguration-ref="shibboleth.SigningConfiguration.SHA1" />

> 
> What I can say for certain is that the below settings *do* work with O365.
> 
> 
> 	    <!--
> 	        Azure AD / Office 365
> 	        Relying Party Configuration
> 	    -->
>        <bean parent="RelyingPartyByName"
>              c:relyingPartyIds="urn:federation:MicrosoftOnline">
>            <property name="profileConfigurations">
>                <list>
>                    <bean parent="SAML2.ECP"
>                          p:encryptAssertions="false"
>                          p:signAssertions="true"
>                          p:signResponses="false"
>                          p:securityConfiguration-ref="SHA1SecurityConfig"
>                          p:nameIDFormatPrecedence="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent" />
>                    <bean parent="SAML2.SSO"
>                          p:encryptAssertions="false"
>                          p:signAssertions="true"
>                          p:signResponses="false"
>                          p:securityConfiguration-ref="SHA1SecurityConfig"
>                          p:nameIDFormatPrecedence="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent" />
>                    <bean parent="SAML2.Logout" p:securityConfiguration-ref="SHA1SecurityConfig" />
>                </list>
>            </property>
>        </bean>
> 


--
Michael A. Grady
IAM Architect, Unicon, Inc.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://shibboleth.net/pipermail/users/attachments/20160331/54516a20/attachment.sig>