11-22-2016 09:50 AM
Scenario
Question:
Thank you -
Solved! Go to Solution.
11-28-2016 12:44 PM
By default they will get all session types available assigned, the IDMS would have to map some attribute flags in the following manner within the SAML Assertion
<ns2:Attribute Name="MT" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified">
<ns2:AttributeValue><10,101,234,543></ns2:AttributeValue>
</ns2:Attribute>
Those comma separated numbers would define those meeting types for that user..
Or you can do a setUser API command after the account is provisioned and change the meeting types to what's required externally from the IDMS.
11-28-2016 12:44 PM
By default they will get all session types available assigned, the IDMS would have to map some attribute flags in the following manner within the SAML Assertion
<ns2:Attribute Name="MT" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified">
<ns2:AttributeValue><10,101,234,543></ns2:AttributeValue>
</ns2:Attribute>
Those comma separated numbers would define those meeting types for that user..
Or you can do a setUser API command after the account is provisioned and change the meeting types to what's required externally from the IDMS.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide