Before
An identity engineer would manually open the request and attachment, interpret the federation settings, and transcribe them into an application configuration. They would then request approval, update the ticket, check each requested group, assign valid groups, and communicate the outcome across separate systems.
How it works
- Receive the ticket request, retrieve its attachment, and analyze the protocol, required values, and requested groups.
- Send the setup proposal for approval, then update the ticket when details are missing or the request is not accepted.
- On approval, create the application, verify the result, assign groups that exist, and report the outcome.
Workflow details
- Request intake: A ticket event provides the request details and ticket identifier. The workflow locates the corresponding request record and attachment, then retrieves the federation information needed for analysis.
- Validation and preparation: The request is analyzed to identify the federation protocol, application label, owner, URLs, requested groups, and any missing or unsupported details. A setup proposal is prepared only from the information supplied in the request and attachment.
- Approval routing: The analysis is sent to an approval conversation in Teams. The workflow uses the response to decide whether to proceed or update the ticket with a request for additional information when the proposal is not accepted or required details are unavailable.
- Application setup: After approval, the workflow submits the prepared configuration to Okta, checks whether the application was created successfully, and records the application label, client ID, and metadata reference in the ticket.
- Group handling and reporting: Requested groups are checked individually. Existing groups are assigned to the new application, missing groups are identified in ticket comments, and the group assignment results are reported back in Teams.
What changed
The request now moves from ticket intake through validation, approval, application setup, and group handling in one workflow. Automated checks determine whether required details and groups are available, while the approval decision remains a human-controlled checkpoint.
Work removed
Opening attachments one by one, transcribing federation settings, checking each requested group, assigning eligible groups, copying application results into the ticket, and manually posting status updates.
Expected outcome
Conservatively, at least four recurring manual actions are removed per request, including configuration transcription, group verification, ticket updates, and result reporting, subject to complete request data and approval.
