Creating a Custom Assertion
Before you begin
You must have the webMethods API Gateway's manage security configurations functional privilege assigned to add a custom assertion.
About this task
You might want to create a custom assertion when you want to:
- Enforce symmetric binding with an authentication mechanism that is not available by default in webMethods API Gateway.
- Support signing and encryption at the desired level.
- Modify the predefined encryption algorithm and security layout properties.
- Enforce custom authentication tokens that are not available by default in webMethods API Gateway.
Important: When creating a custom assertion, make sure that
both the syntax and the semantics of the assertion element are valid and in
compliance with the Web Services Security Policy specification.
To create a custom assertion
Procedure
What to do next
To enforce the custom binding or token assertion in an API, select the assertion in the appropriate fields of the Inbound Auth - Message policy:
- Binding Assertion
- Custom Token Assertion
To enforce the custom policy assertion in an API, select the assertion and the corresponding SAML issuer in the appropriate fields:
- Issuer Policy field of the Add SAML Issuer configuration page.
- Authentication scheme field of the Outbound Auth - Message policy.