Shib v4 hybrid proxying via Azure AD

[Michael Grady]

> On Mar 1, 2021, at 2:54 PM, Jeffrey Williams via users <users at shibboleth.net> wrote:
> 
> I have this running in our val environment and ran into that error in the past.  For us, it was having to do with Shib not being configured to parse the returned attribute to be used to poll your attribute source.
> 
> For starters, confirm that you have the c14n/attribute bean uncommented in conf/c14n/subject-c14n.xml.  I don't think that's expressly given in the docs.
> 
> -Jeff
> 
> On Mon, Mar 1, 2021 at 2:33 PM Goggins, Patrick via users <users at shibboleth.net <mailto:users at shibboleth.net>> wrote:
> Building up a new Shib v4.0.1 IdP (under WS2019) utilizing Azure AD for a hybrid release.
> 
> Finished running through the documentation steps a few days ago but running into some issues with crosswalk mapping. I’ve enabled SAML debugging to isolate the issue but not sure where the adjustment needs to be made.
> 


Anybody doing this should read the excellent page that Chris Phillips and the Canadian Access Federation added to the Shib wiki about doing this:

  https://wiki.shibboleth.net/confluence/display/KB/Using+SAML+Proxying+in+the+Shibboleth+IdP+to+connect+with+Azure+AD <https://wiki.shibboleth.net/confluence/display/KB/Using+SAML+Proxying+in+the+Shibboleth+IdP+to+connect+with+Azure+AD>

I was going to write up a page, but they pointed me to the work they had in progress,  and it really covers everything you need to know and be aware of when doing this.

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



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20210301/5872c33d/attachment.htm>