# SAML 2.0 IdP Type Implemented **URL:** \ **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:** 8
**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:** [April 7, 2021, 3:37pm UTC](https://forum.inductiveautomation.com/t/saml-2-0-idp-type-implemented/23051/8 "2021-04-07T15:37:03Z")
Do you have a `Value is not a collection` exception in your gateway logs? If so, you are probably running into the issue which was fixed by ticket number 1677 mentioned here: [Nightly 8.1 Changelogs - 2021 - #51 by KathyApplebaum](http://forum.inductiveautomation.com/t/nightly-8-1-changelogs-2021/42410/51) (which is currently available in the 8.1.5 nightly build). If you are able to upgrade, you could use the new `multi-attribute-source` bound expression path prefix to signal to the system that you are expecting the attribute value returned to be a multi-valued collection. Example: `containsAny({multi-attribute-source:authnResponse:/saml2p:Response/saml2:Assertion/saml2:AttributeStatement/saml2:Attribute[@Name='AD_Groups']/saml2:AttributeValue/text()},"Admin")` --- _[View the full topic](https://forum.inductiveautomation.com/t/saml-2-0-idp-type-implemented/23051)._