![]() ![]() To use a new or existing personal access token or SSH key with an organization that uses or enforces SAML SSO, you will need to authorize the token or authorize the SSH key for use with a SAML SSO organization. For more information, see " Creating a personal access token" or " Generating a new SSH key and adding it to the ssh-agent." If you don't have a personal access token or an SSH key, you can create a personal access token for the command line or generate a new SSH key. To use the API or Git on the command line to access protected content in an organization that uses SAML SSO, you will need to use an authorized personal access token over HTTPS or an authorized SSH key. For more information, see " Viewing and managing your active SAML sessions." You can view and manage your active SAML sessions in your security settings. This periodic login requirement limits the length of access and requires you to re-identify yourself to continue. ![]() The duration of this login period is specified by your IdP and is generally 24 hours. You must periodically authenticate with your SAML IdP to authenticate and gain access to the organization's resources on. If you haven't recently authenticated with your organization's SAML IdP in your browser, you must authenticate at the SAML IdP before you can access the organization. If you have recently authenticated with your organization's SAML IdP in your browser, you are automatically authorized when you access a GitHub organization that uses SAML SSO. For more information on outside collaborators, see " Roles in an organization." ![]() Note: Outside collaborators aren't required to authenticate with an IdP to access the resources in an organization with SAML SSO. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
May 2023
Categories |