Dev/Staging SSO Key
W
Willow Wolf
Hey there, just embarking on my first embedded Canny integration. Maybe I'm missing something, but is there a dev or staging variant of the SSO key?
Do not want to mix up test environment user IDs and metadata with production users when I'm testing out the integration.
Andrew Rasmussen
Hey Ethan, thanks for posting. We don't currently have a staging variant of the SSO key. Would you mind elaborating on the problem here? I don't quite understand what's wrong with single signing in as a test user.
W
Willow Wolf
Andrew Rasmussen: Maybe Canny does not actually have any trouble dealing with this. But say, in my staging environment, I have a test user with id=1 and name "Test User", but in the production environment, there is a different user with id=1 and name "Real Person."
Is Canny going to have trouble resolving things if I post some test feedback in the test environment, and then "Real Person" tries to post feedback in the production environment?
I guess I would appreciate some clarification around how Canny would handle such a collision of user IDs. Maybe I am thinking about this the wrong way, and I should instead have a test/staging
board
and a production board
? Are users identified uniquely per-board or per subdomain?Andrew Rasmussen
Willow Wolf: We haven't documented this yet, but here's how SSO handles collisions:
- If there's already a user account with this userID, use that
- Else if there's already a user account with this email, use that
- Else create a new user
User accounts will collide across boards (and companies!) so in your case, your "Real Person" account would collide with your "Test User" account. An easy fix here would be to prefix your userIDs with something like "test_" in your test environment. This will avoid the collision.
Would that work for you?
W
Willow Wolf
Andrew Rasmussen: Yeah, that works, good to know, thanks.