# SAML 2.0 IdP Type Implemented

**URL:** <https://forum.inductiveautomation.com/t/saml-2-0-idp-type-implemented/23051>\
**Category:** Ignition Early Access\
**Created:** [March 4, 2019, 11:23pm UTC](https://forum.inductiveautomation.com/t/saml-2-0-idp-type-implemented/23051 "2019-03-04T23:23:52Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jspecht](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jspecht/32/6465_2.png) [@jspecht](https://forum.inductiveautomation.com/u/jspecht)\
**Post date:** [March 4, 2019, 11:30pm UTC](https://forum.inductiveautomation.com/t/saml-2-0-idp-type-implemented/23051/2 "2019-03-04T23:30:38Z")

</div>

One thing to note: in user attribute mappings and security level rules, you must access attributes in the SAML response document using an xPath expression, such as `/saml2p:Response/saml2:Assertion/saml2:Subject/saml2:NameID/text()`. This is because the SAML response is an XML document whereas in OpenID Connect, we use a JSON Path because the response is a JSON-encoded ID token.

---

_[View the full topic](https://forum.inductiveautomation.com/t/saml-2-0-idp-type-implemented/23051)._