Listen to this Post
2024-12-11
Tired of juggling multiple tools for managing your organization’s security? We’ve got exciting news! As part of our commitment to providing a more streamlined and powerful experience, we’re retiring the dedicated Security Manager API and introducing the all-encompassing Organization Roles API.
This new API offers a robust set of features, allowing you to effortlessly manage not only Security Managers but also all other roles within your organization.
What’s Changing?
The Security Manager API, with its specific endpoints for managing security manager teams, will be retired in 12 months. Don’t fret, though! The Organization Roles API provides a seamless replacement with enhanced functionality.
Heres a breakdown of whats affected:
Retired Endpoints: These endpoints will cease to be functional after December 31st, 2025 (for GitHub.com) and after GitHub Enterprise Server version 3.20.
GET /orgs/{org}/security-managers/teams
PUT /orgs/{org}/security-managers/teams/{team_slug}
DELETE /orgs/{org}/security-managers/teams/{team_slug}
Your New Go-To:
The Organization Roles API empowers you to manage all roles within your organization, including Security Managers. It offers the following endpoints as replacements:
GET /orgs/{org}/roles: Retrieves all roles within your organization.
GET /orgs/{org}/roles/{role_id}/teams: View teams associated with a specific role.
PUT /orgs/{org}/roles/{role_id}/teams/{team_slug}: Assign a team to a particular role.
DELETE /orgs/{org}/roles/{role_id}/teams/{team_slug}: Remove a team from a role.
Ready to Make the Switch?
You can start utilizing the Organization Roles API on GitHub.com today. For GitHub Enterprise Server users, version 3.16 and later will fully support the Security Manager role within the Organization Roles API.
We encourage you to explore the comprehensive documentation for the Organization Roles API and provide valuable feedback to help us continuously improve your experience.
What Undercode Says:
This shift towards the Organization Roles API presents several advantages:
Centralized Management: Manage all roles (including Security Managers) from a single, unified API. This simplifies your workflow and eliminates the need to juggle separate tools.
Enhanced Functionality: The Organization Roles API offers additional capabilities beyond managing teams for Security Managers. This allows for a more granular control over access permissions across your organization.
Future-Proofing: By transitioning to the Organization Roles API,
We believe this change will empower you to streamline security management processes and enhance overall control within your organization.
Additional Analytics:
The retirement of the Security Manager API signifies a shift towards a more comprehensive and future-proof approach to role management. This new API is likely to gain wider adoption due to its centralized capabilities. As organizations continue to prioritize security and access control, the Organization Roles API positions itself as a valuable tool for managing user permissions effectively.
References:
Reported By: Github.blog
https://www.digitaltrends.com
Wikipedia: https://www.wikipedia.org
Undercode AI: https://ai.undercodetesting.com
Image Source:
OpenAI: https://craiyon.com
Undercode AI DI v2: https://ai.undercode.help
