What’s the timeout threshold on webhooks?
Lumos waits 15 seconds for a webhook to respond before treating it as a timeout. Webhooks do not retry, so a timed-out request is considered failed/unsuccessful in Lumos, even if the workflow or process succeeds in the service provider for each retry. When a provisioning webhook times out, Lumos still tries to assign the employee the access was requested for to any IdP apps or IdP/email groups associated with the request. See Provisioning Webhooks. After trying to add the user to the IdP/email groups, Lumos always creates a manual provisioning task for the App Admins to act on. Lumos assumes that some part of the provisioning workflow failed and needs manual action. See Confirming Provisioning For Access Requests.Can I modify the content of the webhook payload?
This is not supported today. The fields and format of a webhook payload are static and cannot be modified when you create the webhook.Are custom intake fields sent in webhooks?
Yes. Lumos sends custom intake fields that you add to an application as part of the webhook payload. This includes request validation, pre-approval, provisioning, and deprovisioning webhooks. If the app does not have custom intake fields configured, the field is sent as:Are custom attributes sent in webhooks?
Custom attributes that you map to a user are not sent as part of the webhook payload today.What is the format of the webhook payload?
The Permission source is always one of the following values:- MICROSOFT_OAUTH
- MICROSOFT_GCC
- GSUITE_OAUTH = “GSUITE_OAUTH”
- OKTA
- MANUAL
- ONELOGIN
- ATLASSIAN
- GOOGLE_CLOUD
- LUMOS_INTEGRATION
- JUMPCLOUD