👷‍♂️
Work
  • 💻SNOW
    • Catalog Forms
    • Knowledge Base
  • ☁️Azure
    • Graph Permissions
    • App Registration Auths
      • Postman
      • Graph ROPC Federated Account
        • MSAL UsernamePasswordCredential
        • Java
        • Python
        • C#/VB code Auth
      • Powershell
      • Java Auth x EWS
      • Python Auth x Sharepoint
      • C# Auth x Sharepoint
    • MFA
    • Dynamic Group
    • AAD Device Pending
    • O365 Device Enrollment
    • AAD Device Troubleshoot
    • AAD Mobile Troubleshooting
    • ADO Service Principal
    • External B2B
    • VLSC Admin
    • PowerBI Session Timeout
    • SSO issues
  • 🔓OKTA
    • SVC Account
    • OKTA Integration
    • Access Issues
  • 👷‍♂️Workday
    • Account Lifecycle
    • Coupa
  • 📨O365
    • OOF of Distribution List
    • Mailbox Recovery
    • Mailbox Existence
  • 🦄Misc
    • Windows Terminal
    • Google Auth Export
    • MS Teams Issues
  • 🌥️Cloud Stuff
    • 🚀Benchmarking
      • Vultr
    • 💳Cloud Server
    • ♻️Email and Spams
  • 🔬Open Source
    • Pending
      • Matrix/Synapse
      • Huginn
      • ChangeDetection
    • Tested
      • Codex Docs
      • Ghost Blog
      • n8n Automation
Powered by GitBook
On this page
  1. OKTA

SVC Account

PreviousSSO issuesNextOKTA Integration

Last updated 2 years ago

For the record, SVC accounts should not be used for interactive logins.

svc_accountname account is in OU in AD that is not synced to Okta and account can't be used to be authenticated to any services integrated with Okta.

Account need to be moved to following OU in AD corp.JABIL.ORG/JBLSystemAndServices/ServiceAccountResourceMailbox/ to be synced in Okta and used to authenticate to O365 etc.

Submit 2 requests, [1] Policy Exception first, then [2] IAM request mentioning request ID from [1] to proceed

🔓
Policy Exception / Identity Access Management Standard
IAM / Okta, CyberArk and General Consultations / Identity and Access Consultation Request