A way to get CSRF tokens should be implemented, this way the client can get one and not worry about managing it. These tokens will need to be treated a bit different than a standard session token of course, so their expiration times should be much shorter.
A way to get CSRF tokens should be implemented, this way the client can get one and not worry about managing it. These tokens will need to be treated a bit different than a standard session token of course, so their expiration times should be much shorter.
The endpoint for this and just about anything like it should probably be guarded by requiring a signed API key, not just allowing an end user that's logged in to fetch tokens as they please.
The endpoint for this and just about anything like it should probably be guarded by requiring a signed API key, not just allowing an end user that's logged in to fetch tokens as they please.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
A way to get CSRF tokens should be implemented, this way the client can get one and not worry about managing it. These tokens will need to be treated a bit different than a standard session token of course, so their expiration times should be much shorter.
The endpoint for this and just about anything like it should probably be guarded by requiring a signed API key, not just allowing an end user that's logged in to fetch tokens as they please.