-
Notifications
You must be signed in to change notification settings - Fork 409
EVE SSO
Ryan Holmes edited this page May 14, 2018
·
2 revisions
This article will describe the purposes of the SSO options available to the user. These options can be configured via Preferences > EVE SSO.
Determines how the user will authenticate with the eve servers. There are two options:
- pyfa.io: This is the setting most people will want for easy integration with ESI. pyfa.io is used as an authentication middle-man. It's able to provide the pyfa client the tokens it needs in order to keep your characters logged in permanently, while also keeping the pyfa's client secret... well, secret. It should be stressed that pyfa.io is simply a proxy for the authentication calls, and acts like any other web application that allows you to login to EVE (that is, your account details are never known to the website). More information on how this mode works can be found here! USE unless you're having problems with this method.
-
Custom application: Allows you to provide pyfa the client details for your own application, set up through the EVE Developers portal. Not everyone may have this option due to legal reasons. USE if you cannot access pyfa.io for some reason (firewall, government censorship, etc), or for those that simply wish to have that "control" (after all, we are all part of e paranoid EVE community ;P)
- Requires you to use
http://localhost:6461
as the Callback URL when setting up your Developer application - Requires these scopes to enable full access to pyfa's features
- Requires the use of a local server. If you're not able to access pyfa.io (thus requiring the use of custom details), and can't spawn a local server to handle the SSO callback (due to computer restrictions)... there's not much you can do right now. If this causes you issues, please get in touch with me and we can work something out. :)
- Requires you to use
This section applies to only those using pyfa.io as the SSO Mode
- Local Server: pyfa will spin up a small local server on localhost with a random unused port number, and send this info to pyfa.io, which will then redirect you to EVE SSO. When EVE SSO redirects you back to pyfa.io, it will attempt to redirect back to your local server address. This request will have the tokens that pyfa needs in order to use ESI functionality
- Manual: Instead of spinning up a server that pyfa.io will redirect to, after logging into EVE SSO, pyfa.io will display a block of text. You can then copy and paste that text into a window that pyfa opens. This chunk of text is basically the same information that would have normally gone to the local server described in the first option. This option is useful if you can't (computer permissions) or don't wish to (paranoia :P), for whatever reason, spawn a small server listening for requests.