Jun 14 • Community
Transition of Red Hat Hybrid Cloud Console APIs from basic authentication to token-based authentication via service accounts
🚨 Heads-up for anyone running Red Hat Ansible Automation Platform in production:
Red Hat is retiring basic authentication in favour of token-based Service Accounts.
If your playbooks, pipelines, or external tools still pass a username/password, they’ll stop working after 31 July 2025.
Why care?
• 15-minute rotating tokens ▶ smaller attack surface
• MFA & SSO friendly ▶ no more ROPC work-arounds
• Granular RBAC ▶ least-privilege by design
What to do (TL;DR):
1️⃣ Create a Service Account in console.redhat.com
2️⃣ Store the Client ID & Secret securely
3️⃣ Add the account to the right User Access group(s)
4️⃣ Switch your integration to the Client Credentials flow
5️⃣ Test & automate token refresh (~10 min cadence)
I’ve walked several enterprises through this migration—usually a half-day effort if you map dependencies early. Don’t wait until July; audit your scripts and CI/CD jobs this sprint and bake the change into your next release cycle.
Full guide ➡️ https://access.redhat.com/articles/7036194
#Ansible #RedHat #DevSecOps #ServiceAccounts #CloudSecurity
0
0 comments
Transition of Red Hat Hybrid Cloud Console APIs from basic authentication to token-based authentication via service accounts
powered by
skool.com/ai-devops-ansible-community-6317
AI DevOps Mastermind by Luca Berton: AI, DevOps, Kubernetes & Terraform. Access 50+ hours of courses, hands-on labs, and career-boosting mentorship!
Suggested communities
Powered by