Extend bridge go-slack documentation for authentication via login-token #61
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For the go slack-bridge, the given documentation that describes the authentication process is a bit sparse.
Slack has enhanced the access-security to a given domain. The
login-password
method will not be handled correctly, since you needto use a 2FA method.
Using
login-token
enables a secure and working solution.Admins are not neccessarily confident to extract the needed
token
and their correspondingcookies
.The PR will the needed steps precisely when consuming the web-browsers
dev-tools
.That should ease the process.
For the go slack-bridge, the given documentation that describes the authentication process is a bit sparse.
Slack has enhanced the access-security to a given domain. The
login-password
method will not be handled correctly, since you needto use a 2FA method.
Using
login-token
enables a secure and working solution.Admins are not neccessarily confident to extract the needed
token
and their correspondingcookies
.The PR will the needed steps precisely when consuming the web-browsers
dev-tools
.That text should ease the process.