Allow adding/merging authentication methods onto one user #2494
Comments
|
This sounds like expected behavior when searching a Google SSO team from within Slack at the moment – It will only search collections with team read access as there is not yet a reliable way to know which Google user the Slack user maps to. If searching private collections from Slack is important to your team I would recommend using Slack SSO for the moment. |
|
Seems impossible to log using Slack instead of Google
[image: image.png]
Le jeu. 26 août 2021 à 16:50, Tom Moor ***@***.***> a écrit :
… This sounds like expected behavior when searching a Google SSO team from
within Slack at the moment – It will only search collections with team read
access as there is not yet a reliable way to know which Google user the
Slack user maps to.
If searching private collections from Slack is important to your team I
would recommend using Slack SSO for the moment.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2494 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVLNC5VJUGHMIDYHSX73NMLT6ZICPANCNFSM5C3G77JA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
--
Benjamin Jarry
***@***.***
06.16.35.02.01
<http://www.rethink-it.fr>
|
|
There would be one case, in which Slack users can be mapped to Google users directly: In case they are using a Google email address. Often in applications where one can link multiple accounts with a single one, the email address is used as primary key for a user. In that scenario, logging in often even works with not-yet-connected providers, if the user endpoint reports an email address that is already associated to a user in the system. Edit: Which is covered in #2244. |
|
Hello
I'm still looking for help on that...
Le jeu. 26 août 2021 à 16:56, Benjamin Jarry ***@***.***>
a écrit :
… Seems impossible to log using Slack instead of Google
[image: image.png]
Le jeu. 26 août 2021 à 16:50, Tom Moor ***@***.***> a
écrit :
> This sounds like expected behavior when searching a Google SSO team from
> within Slack at the moment – It will only search collections with team read
> access as there is not yet a reliable way to know which Google user the
> Slack user maps to.
>
> If searching private collections from Slack is important to your team I
> would recommend using Slack SSO for the moment.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#2494 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AVLNC5VJUGHMIDYHSX73NMLT6ZICPANCNFSM5C3G77JA>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
> .
>
--
Benjamin Jarry
***@***.***
06.16.35.02.01
<http://www.rethink-it.fr>
--
Benjamin Jarry
***@***.***
06.16.35.02.01
<http://www.rethink-it.fr>
|
Then it should work as we are using google account to log into Slack.... |
|
This seems like a solid win as long as the email address is verified by the SSO provider we can safely add the authentication method to any existing user on the team with the same email. |
|
so what should I do now?
Le jeu. 14 oct. 2021 à 08:52, Tom Moor ***@***.***> a écrit :
… This seems like a solid win as long as the email address is verified by
the SSO provider we can safely add the authentication method to any
existing user on the team with the same email.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2494 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVLNC5TRBRS4X3IBOYH5FE3UGZ42BANCNFSM5C3G77JA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Benjamin Jarry
***@***.***
06.16.35.02.01
<http://www.rethink-it.fr>
|
|
We have this exact same problem. We use the same email id for Slack and Google Suite. Currently Outline treats the same id differently depending on the auth chosen. Thus, I need to either use Slack auth to gain Slack functionality, or Google auth to ensure security. Even when its the same email id. We'd love it if you could figure out a way to "merge" a user if they have the same email id. |
|
Same problem for us at Sprinklr. I was going nuts and then stumbled upon this issue! |
|
any news on that ?
Le ven. 25 févr. 2022 à 15:09, Praveen Puglia ***@***.***> a
écrit :
… Same problem for us at Sprinklr. I was going nuts and then stumbled upon
this issue!
—
Reply to this email directly, view it on GitHub
<#2494 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVLNC5VKNWL4XYHGZJNXFF3U46EQ3ANCNFSM5C3G77JA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Benjamin Jarry
***@***.***
06.16.35.02.01
<http://www.rethink-it.fr>
|
|
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days |
|
Does anybody work on this?
Le ven. 15 juil. 2022 à 04:15, github-actions[bot] ***@***.***>
a écrit :
… This issue is stale because it has been open 90 days with no activity.
Remove stale label or comment or this will be closed in 5 days
—
Reply to this email directly, view it on GitHub
<#2494 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVLNC5W5QQXN45HOJ5S67BLVUDCVHANCNFSM5C3G77JA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Signing up with email and SSO will now result in one account being created rather than two. Noone has worked on merging two existing accounts yet, it's not something that has come up as a priority from customers. |
|
I got that
But then what is the solution for us, where slack and outline don't
communicate because of login with Google?
Le ven. 15 juil. 2022 à 09:36, Tom Moor ***@***.***> a écrit :
… Signing up with email and SSO will now result in one account being created
rather than two. Noone has worked on merging two existing accounts yet,
it's not something that has come up as a priority from customers.
—
Reply to this email directly, view it on GitHub
<#2494 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVLNC5SCGV6DN5QR6NMK5G3VUEIHDANCNFSM5C3G77JA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days |
|
Still got the issue
Le dim. 13 nov. 2022 à 03:14, github-actions[bot] ***@***.***>
a écrit :
… This issue is stale because it has been open 90 days with no activity.
Remove stale label or comment or this will be closed in 5 days
—
Reply to this email directly, view it on GitHub
<#2494 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVLNC5R6Y3IOGRHD4PFMA43WIBFGPANCNFSM5C3G77JA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days |
|
Issue still exists
Le mer. 15 mars 2023 à 02:58, github-actions[bot] ***@***.***>
a écrit :
… This issue is stale because it has been open 90 days with no activity.
Remove stale label or comment or this will be closed in 5 days
—
Reply to this email directly, view it on GitHub
<#2494 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVLNC5VS2EMQ2OIS5ULTMATW4EO5XANCNFSM5C3G77JA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days |
|
Still valid
Le ven. 14 juil. 2023 à 04:10, github-actions[bot] ***@***.***>
a écrit :
… This issue is stale because it has been open 90 days with no activity.
Remove stale label or comment or this will be closed in 5 days
—
Reply to this email directly, view it on GitHub
<#2494 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVLNC5XY6FJKUSY6GKKYC73XQCS77ANCNFSM5C3G77JA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days |
|
Still exist
Le lun. 13 nov. 2023 à 02:48, github-actions[bot] ***@***.***>
a écrit :
… This issue is stale because it has been open 90 days with no activity.
Remove stale label or comment or this will be closed in 5 days
—
Reply to this email directly, view it on GitHub
<#2494 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVLNC5WZBOBNAIKBOIAHXPLYEF353AVCNFSM5C3G77JKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBQG4ZTKNZVHA3A>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days |
|
I guess it is still valid
Le jeu. 14 mars 2024 à 02:46, github-actions[bot] ***@***.***>
a écrit :
… This issue is stale because it has been open 90 days with no activity.
Remove stale label or comment or this will be closed in 5 days
—
Reply to this email directly, view it on GitHub
<#2494 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVLNC5X6EE76R3HUS5QG56TYYD6QJAVCNFSM5C3G77JKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJZGYZDIMZVGQ2Q>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I also need this function. When I set up Outline originally, Google workspace/Slack were the only auth supported. None of my users use either, my group uses Discord. I'd like to switch to Discord SSO but it seems like this isn't possible without a way to map existing accounts to new auth. |
|
One note – if folks have the same email address then the mapping will happen automatically |
How should users who do not have matching emails be handled? Looking at users.update this doesn't seem possible to change an email associated with an account in Outline at the moment. Lots of people change emails for mundane reasons like job/name change, but would also help some of the issue in this thread with migrating organizations/auth providers. Ideally users would be able to manage this themselves from their Profile page within Outline, or as an Admin option on the Members page. |
|
Supporting address changes and verification of changed emails would be separate issues, I suppose. Would you like to write them for us? |
|
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days |
|
While the primary use case appears to be to merge guest accounts that
were invited via email and have since been converted into SSO
accounts, it has also become convenient to link multiple accounts in
other interfaces.
Discourse, GitLab and StackOverflow/StackExchange are prime examples
where this works well.
…On Sun, 22 Sept 2024 at 04:04, github-actions[bot] ***@***.***> wrote:
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
|
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days |
This comment has been minimized.
This comment has been minimized.
|
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days |
|
Still useful. Look at how GitLab and Discourse do it.
…On Sun, 25 May 2025 at 04:15, github-actions[bot] ***@***.***> wrote:
*github-actions[bot]* left a comment (outline/outline#2494)
<#2494 (comment)>
This issue is stale because it has been open 90 days with no activity.
Remove stale label or comment or this will be closed in 5 days
—
Reply to this email directly, view it on GitHub
<#2494 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMRV7AQZJLXJWI5TE3OOE33AERTLAVCNFSM5C3G77JKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEOJQG42TKOJRHAZA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
A clear and concise description of what the bug is.
instance : https://rethink-it.getoutline.com/
To Reproduce
we use :
I identified into Outline with Google credentials
I added Outline to slack
(rethinkitfr.slack.com)
When trying to use /outline on the slack gives :
No results for "congés" (It looks like you haven’t signed in to Outline yet, so results may be limited)
We already face this problem
Expected behavior
Screenshots
Outline (please complete the following information):
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: