| Pages: [1] :: one page |
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Talos Katuma
Helion Production Labs
Mildly Intoxicated
8
   |
Posted - 2013.04.27 09:03:00 -
[1] - Quote
I followed some of the developer talks from fanfest. One thing I noticed and wondering if there's been thoughts on that already. SSO and later crest which will build up on this credentials. Seems to be focused on character level.
Now for quite a lot of tools it's actually necessary/useful to have multiple characters. At the moment it's necessary to add one api key per account (for people with multiple accounts). If I followed the discussions correctly, to use crest apis, people would need to authenticate each individual character.
Have there been thoughts to make this usecase simpler (maybe by allowing to at least select all characters when giving access to them, or even across accounts). |
Dino Boff
Lead Farmers
Kill It With Fire
27
|
Posted - 2013.04.27 11:41:00 -
[2] - Quote
Note that it's not that bad (I am guessing). Once a user authorise access to one character, if he try to authorise access to an other character on the same account soon enough after, he will still be logged in on his account and will just need to select an character and click a button. |
Talos Katuma
Helion Production Labs
Mildly Intoxicated
8
|
Posted - 2013.04.27 13:18:00 -
[3] - Quote
Nut too sure about this, might actually be more problematic, if you already have an authenticated session and then try to reauthenticate with another character. |
Manhim
Cyan Ventures
2
|
Posted - 2013.04.30 18:05:00 -
[4] - Quote
Just keep the keys in a database linked to the character, not the account or the user. |
Tonto Auri
Vhero' Multipurpose Corp
135
|
Posted - 2013.04.30 19:45:00 -
[5] - Quote
Note that api-key-per-character allow for more transparent handling of cases such as character move.
The two most common elements in the universe are hydrogen and stupidity.
---áHarlan Ellison |
Talos Katuma
Helion Production Labs
Mildly Intoxicated
8
|
Posted - 2013.04.30 20:33:00 -
[6] - Quote
I see mostly an issue when people try to add an additional character and they already are logged in and authenticated with a different character. I think there are a lot of tools where you don't want to have one website account per character, but one account where various characters are listed, maybe even from different accounts.
With the current api this works easy, even if you want to have one key per character, with crest where the authorization is done with oauth2 this might not work as easily.
Example:
Site redirects for auth to eve sso,
player selects character1 and authorizes,
Redirect back to site happens and site registers refresh token for character1
Now how would a second character be added?
If site would redirect for auth to eve sso again wouldn't the existing auth permission with character1 automtically be taken? |
| |
|
| Pages: [1] :: one page |
| First page | Previous page | Next page | Last page |