> Markdown version of [/jobs/ext/2010826-secret-clearance-migration-engineer](https://www.wearedevelopers.com/jobs/ext/2010826-secret-clearance-migration-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Secret Clearance Migration Engineer

- **Company:** Leidos, Inc.
- **Location:** Elko New Market, MN, United States
- **Experience:** Expert
- **Contract:** Permanent contract
- **Skills:** Cyber Security, Identity and Access Management, NIPRNet, OAuth, Security Assertion Markup Language (SAML), Systems Integration, Enterprise Software Applications, Okta, SC Clearance, Information Technology, SailPoint
- **Published:** August 10, 2026
- **Apply:** https://careersingovernment.com/job/2425017/secret-clearance-migration-engineer-42/

## About the Role

using SAML, OAuth 2.0, or OIDCHands-on experience with Identity Provider (IdP) or Identity Governance and Administration (IGA) platformsActive Secret clearance and ability to meet DoD cybersecurity training requirements

## Description

Supporting a critical Government Identity, Credential, and Access Management initiative, the remote Secret Clearance Migration Engineer will execute the integration and onboarding of NIPRNet applications onto a centralized ICAM technical stack, leveraging Okta and SailPoint technologies.Key responsibilities:Execute technical integration of NIPRNet applications into the ICAM stack, ensuring secure user authentication and access managementConduct technical triage of applications, documenting integration gaps and determining enablement pathwaysProvide technical advisement to Application Owners on configuring applications for the ICAM platform, ensuring compliance with security requirementsRequired qualifications:Bachelor's degree in Computer Science, Information Technology, Cybersecurity, or a related fieldMinimum of 4 years of IT experience, including 2 years in identity and access management or enterprise application integrationExperience configuring and troubleshooting SSO integrations


## Related Videos

- [Keeping applications secure by evolving OAuth 2.0 and OpenID Connect](https://www.wearedevelopers.com/videos/100152-keeping-applications-secure-by-evolving-oauth-2-0-and-openid-connect)
- [Delegating the chores of authenticating users to Keycloak](https://www.wearedevelopers.com/videos/1558-delegating-the-chores-of-authenticating-users-to-keycloak)
- [Delay the AI Overlords: How OAuth and OpenFGA Can Keep Your AI Agents from Going Rogue](https://www.wearedevelopers.com/videos/1637-delay-the-ai-overlords-how-oauth-and-openfga-can-keep-your-ai-agents-from-going-rogue)
- [Security Pitfalls for Software Engineers](https://www.wearedevelopers.com/videos/726-security-pitfalls-for-software-engineers)
- [Advanced Cypress: custom assertions and tasks](https://www.wearedevelopers.com/videos/790-advanced-cypress-custom-assertions-and-tasks)
- [Migrating half a million users to a new payment service provider](https://www.wearedevelopers.com/videos/730-migrating-half-a-million-users-to-a-new-payment-service-provider)

## Related Articles

- [Fully Remote Software Engineer Jobs](https://www.wearedevelopers.com/magazine/447-fully-remote-software-engineer-jobs)
- [Dev Digest 191: Malware interviews, EU ❤️ Open Source and Skilled Agents](https://www.wearedevelopers.com/magazine/645-dev-digest-191-malware-interviews-eu-open-source-and-skilled-agents)
- [Dev Digest 210: AI Agents Are Go! Is MCP Dead? LLMs Crack Anonymity](https://www.wearedevelopers.com/magazine/709-dev-digest-210-ai-agents-are-go-is-mcp-dead-llms-crack-anonymity)
- [9 Ways to Make Money Hacking](https://www.wearedevelopers.com/magazine/333-9-ways-to-make-money-hacking)
- [Dev Digest 134 - Where pixels sing?](https://www.wearedevelopers.com/magazine/477-dev-digest-134-where-pixels-sing)
- [Events like RSAC Get You CISOs. Developers Decide What Actually Gets Deployed.](https://www.wearedevelopers.com/magazine/693-events-like-rsac-get-you-cisos-developers-decide-what-actually-gets-deployed)