Jump to content
Updated Privacy Statement

Jens Beyer

Members
  • Posts

    3
  • Joined

  • Last visited

Everything posted by Jens Beyer

  1. So you could give it a try with expression "AAA.USER.NAME". Did not try it yet but the description looks like match. Just found this some days ago. Another way when assuming you are using Azure Enterprise Apps. Try creating a custom entry in SAML SSO settings under "Attributes & Claims" for example name "MyCustomUPN" and value "user.userprincipalname". In your SAML server/action add this attribut to form field "Attributes" under "More" (comma seperated list if you have more then one). So this value is then requested via SAML This received attribute can then be used in expressions after the SAML auth is done like "AAA.USER.ATTRIBUTE("MyCustomUPN"). This will not work with the default attributes. Did only work with custom ones for me! Hope that helps somehow or points you in some right directions.
  2. Second policy with TRUE is not needed at all. As long you are not on the subnet you are blocking it just gives you access. Not needed to configure that explicitly at the end.
  3. It's there for me when browsing CNS-420 page. Temporary problem? Anyway direct link to 440 exam: https://training.citrix.com/learning/exam?id=1944
×
×
  • Create New...