Home labs & practical projects
Trace an application sign-in through its identity flow
A project to do with your own tools, with guidance on what to create and capture.
What you could create
A new support analyst needs to explain why a user can sign into the identity portal but cannot access a particular application.
| Evidence | What to capture |
|---|---|
| Application sign-in troubleshooting map | Show the inputs, scope and decisions behind this record. Portal access is not assumed to grant application access. |
| Support handover note | Include the evidence supporting your conclusion. The escalation includes timestamps and identifiers without secrets. |
What you'll need
Document, spreadsheet or diagram tool
Draw a fictional user, Okta tenant and application. Include user status, group membership, application assignment and a sample failed sign-in record.
Project record
Keep the working files for application sign-in troubleshooting map and record assumptions as you go.
Current reference material
Use the linked provider resources to verify the features, access terms and version relevant to your project.
Access & cost
No paid platform is needed for the written version. Use a document, spreadsheet or diagram tool you already have.
The organisation and records are fictional. Write down assumptions; do not substitute confidential employer information.
Suggested milestones
- 1
Plan and investigate
Trace the difference between identity authentication and application assignment.
- 2
Develop your approach
Identify the evidence needed to distinguish a policy failure from an application-side failure.
- 3
Verify and explain
Write a support response and escalation package without requesting the user’s password.
Useful resources
Use these resources to deepen your understanding and check key details.
A useful starting point
Draw a fictional user, Okta tenant and application. Include user status, group membership, application assignment and a sample failed sign-in record.
What a good result looks like
- Portal access is not assumed to grant application access.
- The escalation includes timestamps and identifiers without secrets.
Finish the project
Keep the decision record and note unanswered questions. A written design is not evidence that a technical control has been tested.
Independent home-project guidance, not an official vendor lab or a claim of complete exam coverage. Use your own tools and label the work accurately.