{"id":105335,"date":"2022-10-19T15:37:19","date_gmt":"2022-10-19T13:37:19","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/github-realizoval-podderzhku-tokenov-dlya-predostavleniya-vyborochnogo-dostupa"},"modified":"2022-10-19T15:37:19","modified_gmt":"2022-10-19T13:37:19","slug":"github-realizoval-podderzhku-tokenov-dlya-predostavleniya-vyborochnogo-dostupa","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/github-realizoval-podderzhku-tokenov-dlya-predostavleniya-vyborochnogo-dostupa","title":{"rendered":"GitHub has implemented support for tokens to provide selective access.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
GitHub has implemented support for a new type of access tokens that can selectively define the permissions of a specific developer or script, covering only the tasks necessary for completing the work. It is expected that selective access provision will help reduce the risk of attacks in the event of credential compromise. Tokens can be used in scripts to manage selective access to the GitHub API and when connecting via HTTPS. Additionally, administrators are provided with options to review and revoke tokens, as well as set auditing policies and token confirmations. <\/p>\n
Previously, a participant could create individual tokens that provided access to all their repositories and organizations, but with the new tokens, project owners can detail access, for example, allowing read-only access or granting selective access to specific repositories. A token can be associated with over 50 permissions covering various operations with organizations, issues, repositories, and users. There is also the option to limit the token's expiration time. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"