Additional attributes in the SDK

To style additional attributes in the SDK, sample data is required. The SDK configuration supports the option to add an additionalAttributes block for every page.

The following example demonstrates, how the mTAN Token Registration Step in the authentication flow can be provided with sample data:

pages: [
 ...
 {
     path: '/auth/flow/{{FLOW}}/mtan/registration/verification/otp',
     additionalAttributes: {
         resendPossible: true,
         phoneNumber: '+41791234567'
     },
     pageSettings: {
         ...
     }
 },
 ...
]

Adding attributes in the SDK only works with attributes that are available on a particular page at the runtime of Airlock IAM.

Sample data added in an additionalAttributes block is only available in the SDK and is not be part of the styling information deployed on an Airlock IAM.

Additional attributes in customized step UIs

Additional attributes can be used in all UI elements that display texts and support translations.

The placeholder property in HTML shows some limitations as it does, by definition of the HTML standard, not accept HTML. The problem only manifests itself if special characters are used in the values of the additional attributes. The SDK transforms special characters into HTML entities. Since placeholders do not accept HTML, those HTML entities are rendered in their "escaped" format and are therefore not displayed correctly.