Third-party authentication

You can let you users authorize to you application through third party solutions. Synerise offers authorization through:

  • Apple
  • Facebook
  • OAuth
Important:
Integration with Google is coming in Q2 2021.

Sign in with Apple


WARNING:
Before configuring the Sign in with Apple authentication, you must implement Sign in with Apple in your application.
Settings for authorizing by Apple
Settings for authorizing by Apple
  1. Go to Settings icon Settings > IAM for applications.
  2. In the Third-party authentication section, click Show.
  3. Switch the Sign-in with Apple toggle on.
  4. In the App bundle identifier field, enter the bundle identifier (it’s a reverse domain name notation).
    Important:
    It’s NOT the AppleID.
  5. Confirm by clicking Apply.

Facebook


Important:
Before you configure Facebook authentication in Synerise, you must implement it in your application.

Currently, there are no dedicated settings related to Facebook authentication on the interface. You just have to implement RESTful API or SDK methods to authenticate through Facebook.

OAuth


OAuth is not the actual OAuth as may be understood per RFC6749: The OAuth 2.0 Authorization Framework. This feature allows you to configure authentication through your existing IT systems that have RESTful APIs, allowing you to authenticate a person through an HTTP call to an endpoint (checking if the provided token is valid and returning a response with the user’s data).

Example response:

  
{
    "Response": {
        "PersonQCCode": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
        "LoyaltyQCCode": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
        "Email": "example.email@example.com",
        "CardNumber": "0000000000000",
        "Role": 8,
        "IsBusiness": false,
        "firstname": "john",
        "lastname": "doe"
    },
    "Success": true,
    "Errors": null
}

Configuring OAuth authorization
Configuring OAuth authorization
  1. Go to Settings icon Settings > IAM for applications.
  2. In the OAuth section, click Show.
  3. In the Endpoint Configuration, in the Endpoint name field, enter the name (it can be anything).
  4. Enter the URL of the endpoint (GET method).
  5. In the Headers section, enter all headers which are required by the endpoint you entered in the previous step.
  6. In the Identification based on OAuth response data section, you can:
    • Leave the settings to default (True) - customID from the OAuth backend is used to authorize a user
    • Set the toggle to False - customID from the application is applied
  7. In the Additional attributes section, from the dropdown list, select the attributes to be passed during the authorization and as the value enter the formula based on this pattern: Response.AttributeName.
    Example additional attributes
    Example additional attributes

Result: According to the example presented in the image, when a customer is authorized, an account is created or updated with the corresponding values from the OAuth authoriation response.

😕

We are sorry to hear that

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

😉

Awesome!

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

Close modal icon Placeholder alt for modal to satisfy link checker