Okta Figma OIN Template Locks Application Username Format When NameID Format Is EmailAddress
Last Updated:
Overview
During the configuration of the Figma Okta Integration Network (OIN) template for Security Assertion Markup Language (SAML) Single Sign-On (SSO), the Application Username Format field locks and prevents customization if the NameID Format is EmailAddress. This occurs because Okta hardcodes certain field dependencies in OIN templates. Resolve this by changing the NameID Format to Username or by creating a Custom SAML application.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Okta Integration Network (OIN)
- Figma
Cause
Okta hardcodes certain field dependencies between the NameID Format and the Application Username Format in OIN templates. Custom SAML applications do not have this restriction.
Solution
What methods exist to customize the Application Username Format for the Figma OIN application?
Customize the Application Username Format by changing the NameID Format within the Figma OIN template or by creating a Custom SAML application.
- To customize the Application Username Format within the Figma OIN template, change the NameID Format to Username.
- If the integration strictly requires the NameID Format to be EmailAddress while also requiring a custom Application Username Format, create a Custom SAML application instead of using the OIN template.
