Sign-in process

By default, your users will be able to sign in with their email address. You can also choose to link your society's login system to the app. This way your members can easily sign in with the credentials they know.

Users sign in through the profile icon on the top right, both on society level and within the event. When clicking Sign in with society account, users are redirected to your OAuth sign in page. If the sign-in succeeds, an account on our servers is created in the background. This account is used to store all the app-related user information, such as saved favorites or chat conversations.

Technical specifications

Our solutions are based on the well-known OAuth2 protocol, using authorization code as the grant type method. To be able to communicate with your system following the OAuth protocol, we need the following parameters.

  • clientID: e.g. 'aclientid'
  • clientSecret: e.g. 'yhgfyefg46fg47ft47fv4vc647fvg47fv'
  • authorizationURL: e.g. 'https://myhost/oauth2/authorize.php'. This is the basic login URL, which we visit providing a special redirect to our server after a successful login. The redirect path receives a code which exchanges for a token at this link. Additional information like redirect URL, clientID, and more are added as query data on the URL.
  • tokenURL: e.g. 'https://myhost/oauth2/token.php'. Here we exchange the code for a valid access token.
  • host: e.g. 'your_host'
  • profilePathURL:  e.g. '/oauth2/profile.php'. We usually ask for a user information endpoint with an e-mail address, first name, last name and a type of identifier, like an ID, which we need to create the Eureka users. This endpoint should be Bearer token protected and can be accessed only with a valid access token per user.

After a successfull OAuth2 authentication, an account is automatically created and given a random password.

Did this answer your question?