Overview
This API has been available since 1.23.0
The LinkedIn identity provider type will use OAuth 2.0 to authenticate a user with LinkedIn. It will also provide a Login with LinkedIn button on FusionAuth’s login page that will direct a user to the LinkedIn login page. Additionally, after successful user authentication, this identity provider will call LinkedIn’s /v2/me and /v2/emailAddress APIs to load additional details about the user and store them in FusionAuth.
The email address returned by the LinkedIn /v2/emailAddress API will be used to create or look up the existing user. Additional claims returned by LinkedIn can be used to reconcile the User to FusionAuth by using a LinkedIn Reconcile lambda. Unless you assign a reconcile lambda to this provider, only the email address will be used from the available claims returned by LinkedIn.
FusionAuth will also store the LinkedIn access_token returned from the login endpoint in the identityProviderLink object, in the identityProviderLink.token field. This object is accessible using the Link API.
The identityProviderLink object stores the token so that you can use it in your application to call LinkedIn APIs on behalf of the user if desired.
1.28.0, the token was stored in the UserRegistration object, in the tokens Map.Create the LinkedIn Identity Provider
Request
URI
The type in the request JSON is used to determine that you are managing the LinkedIn identity provider.
Request Body
The configuration for each Application that the identity provider is enabled for.
This is an optional Application specific override for the top level buttonText.
This is an optional Application specific override for the top level client_id.
This is an optional Application specific override for the top level client_secret.
Determines if a UserRegistration is created for the User automatically or not. If a user doesn’t exist in FusionAuth and logs in through an identity provider, this boolean controls whether or not FusionAuth creates a registration for the User in the Application they are logging into.
Determines if this identity provider is enabled for the Application specified by the applicationId key.
This is an optional Application specific override for the top level scope.
The top-level button text to use on the FusionAuth login page for this Identity Provider.
The top-level LinkedIn client id for your Application. This value is retrieved from the LinkedIn developer website when you set up your LinkedIn app.
Determines if debug is enabled for this provider. When enabled, an Event Log is created each time this provider is invoked to reconcile a login.
This is useful for debugging purposes, but is not intended to be left on during production. It should be enabled during integration or if you are experiencing an issue with this identity provider.
The top-level client secret to use with the LinkedIn Identity Provider when retrieving the long-lived token. This value is retrieved from the LinkedIn developer website when you set up your LinkedIn app.
Determines if this provider is enabled. If it is false then it will be disabled globally.
The unique Id of the lambda to used during the user reconcile process to map custom claims from the external identity provider to the FusionAuth user.
The specified Lambda Id must be of type LinkedInReconcile.
The linking strategy to use when creating the link between the LinkedIn Identity Provider and the user.
The possible values are:
CreatePendingLink- Do not automatically link, instead return a pending link identifier that can be used to link to an existing user.LinkAnonymously- Always create a link based upon the unique Id returned by the identify provider. A username or email is not required and will not be used to link the user. A reconcile lambda will not be used in this configuration.LinkByEmail- Link to an existing user based upon email. A user will be created with the email returned by the identity provider if one does not already exist.LinkByEmailForExistingUser- Only link to an existing user based upon email. A user will not be created if one does not already exist with email returned by the identity provider.LinkByUsername- Link to an existing user based upon username. A user will be created with the username returned by the identity provider if one does not already exist.LinkByUsernameForExistingUser- Only link to an existing user based upon username. A user will not be created if one does not already exist with username returned by the identity provider.
The top-level scope that you are requesting from LinkedIn.
This field must be set to LinkedIn.
Example LinkedIn Request JSON
{
"identityProvider": {
"applicationConfiguration": {
"1c212e59-0d0e-6b1a-ad48-f4f92793be32": {
"createRegistration": true,
"enabled": true
}
},
"buttonText": "Login with LinkedIn",
"client_id": "86b3nbfinbhrnl",
"client_secret": "gAi3V7mC2LGzriQR",
"debug": false,
"enabled": true,
"scope": "r_emailaddress r_liteprofile",
"tenantConfiguration": {
"e872a880-b14f-6d62-c312-cb40f22af465": {
"limitUserLinkCount": {
"enabled": false,
"maximumLinks": 42
}
}
},
"type": "LinkedIn"
}
}Response
Response Codes| Code | Description |
|---|---|
| 200 | The request was successful. The response will contain a JSON body. |
| 400 | The request was invalid and/or malformed. The response will contain an Errors JSON Object with the specific errors. This status will also be returned if a paid FusionAuth license is required and is not present. |
| 401 | You did not supply a valid Authorization header. The header was omitted or your API key was not valid. The response will be empty. See Authentication. |
| 500 | There was an internal error. A stack trace is provided and logged in the FusionAuth log files. The response will be empty. |
Response Body
The configuration for each Application that the identity provider is enabled for.
This is an optional Application specific override for the top level buttonText.
This is an optional Application specific override for the top level client_id.
This is an optional Application specific override for the top level client_secret.
Determines if a UserRegistration is created for the User automatically or not. If a user doesn’t exist in FusionAuth and logs in through an identity provider, this boolean controls whether or not FusionAuth creates a registration for the User in the Application they are logging into.
Determines if this identity provider is enabled for the Application specified by the applicationId key.
This is an optional Application specific override for the top level scope.
The top-level button text to use on the FusionAuth login page for this Identity Provider.
The Linked client id for your App. This value is retrieved from the LinkedIn developer website when you set up your LinkedIn App.
The top-level client secret to use with the LinkedIn Identity Provider when retrieving the long-lived token. This value is retrieved from the LinkedIn developer website when you set up your LinkedIn App.
Determines if debug is enabled for this provider. When enabled, each time this provider is invoked to reconcile a login an Event Log will be created.
Determines if this provider is enabled. If it is false then it will be disabled globally.
The Id of the LinkedIn identity provider, which will always be 6177c09d-3f0e-4d53-9504-3600b1b23f46.
The instant that the provider was added to the FusionAuth database.
The instant that the provider was updated in the FusionAuth database.
The linking strategy to use when creating the link between the LinkedIn Identity Provider and the user.
The possible values are:
CreatePendingLink- Create pending link.Disabled- Disables linking automatically. Available since1.37.0.LinkAnonymously- Anonymous Link.LinkByEmail- Link on email. Create the user if they do not exist.LinkByEmailForExistingUser- Link on email. Do not create the user if they do not exist.LinkByUsername- Link on username. Create the user if they do not exist.LinkByUsernameForExistingUser- Link on username. Do not create the user if they do not exist.
The name of the provider, this field will always be set to LinkedIn.
The top level scope that you are requesting from LinkedIn.
The type of this provider, this field will always be set to LinkedIn.
Example LinkedIn Response JSON
{
"identityProvider": {
"applicationConfiguration": {
"1c212e59-0d0e-6b1a-ad48-f4f92793be32": {
"createRegistration": true,
"enabled": true
}
},
"buttonText": "Login with LinkedIn",
"client_id": "86b3nbfinbhrnl",
"client_secret": "gAi3V7mC2LGzriQR",
"debug": false,
"enabled": true,
"id": "6177c09d-3f0e-4d53-9504-3600b1b23f46",
"insertInstant": 1595361142909,
"lastUpdateInstant": 1595361143101,
"name": "LinkedIn",
"scope": "r_emailaddress r_liteprofile",
"tenantConfiguration": {
"e872a880-b14f-6d62-c312-cb40f22af465": {
"limitUserLinkCount": {
"enabled": false,
"maximumLinks": 42
}
}
},
"type": "LinkedIn"
}
}Retrieve the LinkedIn Identity Provider
There is only one LinkedIn Identity Provider, so this Identity Provider may be retrieved by type or Id.
Request
URI
?type=LinkedInURI
6177c09d-3f0e-4d53-9504-3600b1b23f46Response
| Code | Description |
|---|---|
| 200 | The request was successful. The response will contain a JSON body. |
| 400 | The request was invalid and/or malformed. The response will contain an Errors JSON Object with the specific errors. This status will also be returned if a paid FusionAuth license is required and is not present. |
| 401 | You did not supply a valid Authorization header. The header was omitted or your API key was not valid. The response will be empty. See Authentication. |
| 404 | The object you requested doesn't exist. The response will be empty. |
| 500 | There was an internal error. A stack trace is provided and logged in the FusionAuth log files. The response will be empty. |
Response Body
The configuration for each Application that the identity provider is enabled for.
This is an optional Application specific override for the top level buttonText.
This is an optional Application specific override for the top level client_id.
This is an optional Application specific override for the top level client_secret.
Determines if a UserRegistration is created for the User automatically or not. If a user doesn’t exist in FusionAuth and logs in through an identity provider, this boolean controls whether or not FusionAuth creates a registration for the User in the Application they are logging into.
Determines if this identity provider is enabled for the Application specified by the applicationId key.
This is an optional Application specific override for the top level scope.
The top-level button text to use on the FusionAuth login page for this Identity Provider.
The Linked client id for your App. This value is retrieved from the LinkedIn developer website when you set up your LinkedIn App.
The top-level client secret to use with the LinkedIn Identity Provider when retrieving the long-lived token. This value is retrieved from the LinkedIn developer website when you set up your LinkedIn App.
Determines if debug is enabled for this provider. When enabled, each time this provider is invoked to reconcile a login an Event Log will be created.
Determines if this provider is enabled. If it is false then it will be disabled globally.
The Id of the LinkedIn identity provider, which will always be 6177c09d-3f0e-4d53-9504-3600b1b23f46.
The instant that the provider was added to the FusionAuth database.
The instant that the provider was updated in the FusionAuth database.
The linking strategy to use when creating the link between the LinkedIn Identity Provider and the user.
The possible values are:
CreatePendingLink- Create pending link.Disabled- Disables linking automatically. Available since1.37.0.LinkAnonymously- Anonymous Link.LinkByEmail- Link on email. Create the user if they do not exist.LinkByEmailForExistingUser- Link on email. Do not create the user if they do not exist.LinkByUsername- Link on username. Create the user if they do not exist.LinkByUsernameForExistingUser- Link on username. Do not create the user if they do not exist.
The name of the provider, this field will always be set to LinkedIn.
The top level scope that you are requesting from LinkedIn.
The type of this provider, this field will always be set to LinkedIn.
Example LinkedIn Response JSON
{
"identityProvider": {
"applicationConfiguration": {
"1c212e59-0d0e-6b1a-ad48-f4f92793be32": {
"createRegistration": true,
"enabled": true
}
},
"buttonText": "Login with LinkedIn",
"client_id": "86b3nbfinbhrnl",
"client_secret": "gAi3V7mC2LGzriQR",
"debug": false,
"enabled": true,
"id": "6177c09d-3f0e-4d53-9504-3600b1b23f46",
"insertInstant": 1595361142909,
"lastUpdateInstant": 1595361143101,
"name": "LinkedIn",
"scope": "r_emailaddress r_liteprofile",
"tenantConfiguration": {
"e872a880-b14f-6d62-c312-cb40f22af465": {
"limitUserLinkCount": {
"enabled": false,
"maximumLinks": 42
}
}
},
"type": "LinkedIn"
}
}Update the LinkedIn Identity Provider
This API is used to update an existing LinkedIn Identity Provider.
You must specify the Id of the LinkedIn Identity Provider you are updating on the URI. There is only one LinkedIn Identity Provider, so this Identity Provider may be updated by type or Id.You must specify all of the properties of the LinkedIn Identity Provider when calling this API with the PUT HTTP method. When used with PUT, this API doesn’t merge the existing LinkedIn Identity Provider and your new data. It replaces the existing LinkedIn Identity Provider with your new data.
Utilize the PATCH HTTP method to send specific changes to merge into an existing LinkedIn Identity Provider.
Request
URI
?type=LinkedInURI
?type=LinkedInAvailable since 1.39.0
When using the PATCH method, you can either use the same request body documentation that is provided for the PUT request for backward compatibility. Or you may use either JSON Patch/RFC 6902] or JSON Merge Patch/RFC 7396. See the PATCH documentation for more information.
Available since 1.12.0
When using the PATCH method, use the same request body documentation that is provided for the PUT request.
The PATCH method will merge the provided request parameters into the existing object, this means all parameters are optional when using the PATCH method and you only provide the values you want changed.
A null value can be used to remove a value.
Patching an Array will result in all values from the new list being appended to the existing list, this is a known limitation to the current implementation of PATCH.
URI
6177c09d-3f0e-4d53-9504-3600b1b23f46URI
6177c09d-3f0e-4d53-9504-3600b1b23f46Available since 1.39.0
When using the PATCH method, you can either use the same request body documentation that is provided for the PUT request for backward compatibility. Or you may use either JSON Patch/RFC 6902] or JSON Merge Patch/RFC 7396. See the PATCH documentation for more information.
Available since 1.12.0
When using the PATCH method, use the same request body documentation that is provided for the PUT request.
The PATCH method will merge the provided request parameters into the existing object, this means all parameters are optional when using the PATCH method and you only provide the values you want changed.
A null value can be used to remove a value.
Patching an Array will result in all values from the new list being appended to the existing list, this is a known limitation to the current implementation of PATCH.
Request Body
The configuration for each Application that the identity provider is enabled for.
This is an optional Application specific override for the top level buttonText.
This is an optional Application specific override for the top level client_id.
This is an optional Application specific override for the top level client_secret.
Determines if a UserRegistration is created for the User automatically or not. If a user doesn’t exist in FusionAuth and logs in through an identity provider, this boolean controls whether or not FusionAuth creates a registration for the User in the Application they are logging into.
Determines if this identity provider is enabled for the Application specified by the applicationId key.
This is an optional Application specific override for the top level scope.
The top-level button text to use on the FusionAuth login page for this Identity Provider.
The top-level LinkedIn client id for your Application. This value is retrieved from the LinkedIn developer website when you set up your LinkedIn app.
Determines if debug is enabled for this provider. When enabled, an Event Log is created each time this provider is invoked to reconcile a login.
This is useful for debugging purposes, but is not intended to be left on during production. It should be enabled during integration or if you are experiencing an issue with this identity provider.
The top-level client secret to use with the LinkedIn Identity Provider when retrieving the long-lived token. This value is retrieved from the LinkedIn developer website when you set up your LinkedIn app.
Determines if this provider is enabled. If it is false then it will be disabled globally.
The unique Id of the lambda to used during the user reconcile process to map custom claims from the external identity provider to the FusionAuth user.
The specified Lambda Id must be of type LinkedInReconcile.
The linking strategy to use when creating the link between the LinkedIn Identity Provider and the user.
The possible values are:
CreatePendingLink- Do not automatically link, instead return a pending link identifier that can be used to link to an existing user.LinkAnonymously- Always create a link based upon the unique Id returned by the identify provider. A username or email is not required and will not be used to link the user. A reconcile lambda will not be used in this configuration.LinkByEmail- Link to an existing user based upon email. A user will be created with the email returned by the identity provider if one does not already exist.LinkByEmailForExistingUser- Only link to an existing user based upon email. A user will not be created if one does not already exist with email returned by the identity provider.LinkByUsername- Link to an existing user based upon username. A user will be created with the username returned by the identity provider if one does not already exist.LinkByUsernameForExistingUser- Only link to an existing user based upon username. A user will not be created if one does not already exist with username returned by the identity provider.
The top-level scope that you are requesting from LinkedIn.
This field must be set to LinkedIn.
Example LinkedIn Request JSON
{
"identityProvider": {
"applicationConfiguration": {
"1c212e59-0d0e-6b1a-ad48-f4f92793be32": {
"createRegistration": true,
"enabled": true
}
},
"buttonText": "Login with LinkedIn",
"client_id": "86b3nbfinbhrnl",
"client_secret": "gAi3V7mC2LGzriQR",
"debug": false,
"enabled": true,
"scope": "r_emailaddress r_liteprofile",
"tenantConfiguration": {
"e872a880-b14f-6d62-c312-cb40f22af465": {
"limitUserLinkCount": {
"enabled": false,
"maximumLinks": 42
}
}
},
"type": "LinkedIn"
}
}Response
The response for this API contains the LinkedIn Identity Provider.
| Code | Description |
|---|---|
| 200 | The request was successful. The response will contain a JSON body. |
| 400 | The request was invalid and/or malformed. The response will contain an Errors JSON Object with the specific errors. This status will also be returned if a paid FusionAuth license is required and is not present. |
| 401 | You did not supply a valid Authorization header. The header was omitted or your API key was not valid. The response will be empty. See Authentication. |
| 404 | The object you are trying to update doesn't exist. The response will be empty. |
| 500 | There was an internal error. A stack trace is provided and logged in the FusionAuth log files. The response will be empty. |
Response Body
The configuration for each Application that the identity provider is enabled for.
This is an optional Application specific override for the top level buttonText.
This is an optional Application specific override for the top level client_id.
This is an optional Application specific override for the top level client_secret.
Determines if a UserRegistration is created for the User automatically or not. If a user doesn’t exist in FusionAuth and logs in through an identity provider, this boolean controls whether or not FusionAuth creates a registration for the User in the Application they are logging into.
Determines if this identity provider is enabled for the Application specified by the applicationId key.
This is an optional Application specific override for the top level scope.
The top-level button text to use on the FusionAuth login page for this Identity Provider.
The Linked client id for your App. This value is retrieved from the LinkedIn developer website when you set up your LinkedIn App.
The top-level client secret to use with the LinkedIn Identity Provider when retrieving the long-lived token. This value is retrieved from the LinkedIn developer website when you set up your LinkedIn App.
Determines if debug is enabled for this provider. When enabled, each time this provider is invoked to reconcile a login an Event Log will be created.
Determines if this provider is enabled. If it is false then it will be disabled globally.
The Id of the LinkedIn identity provider, which will always be 6177c09d-3f0e-4d53-9504-3600b1b23f46.
The instant that the provider was added to the FusionAuth database.
The instant that the provider was updated in the FusionAuth database.
The linking strategy to use when creating the link between the LinkedIn Identity Provider and the user.
The possible values are:
CreatePendingLink- Create pending link.Disabled- Disables linking automatically. Available since1.37.0.LinkAnonymously- Anonymous Link.LinkByEmail- Link on email. Create the user if they do not exist.LinkByEmailForExistingUser- Link on email. Do not create the user if they do not exist.LinkByUsername- Link on username. Create the user if they do not exist.LinkByUsernameForExistingUser- Link on username. Do not create the user if they do not exist.
The name of the provider, this field will always be set to LinkedIn.
The top level scope that you are requesting from LinkedIn.
The type of this provider, this field will always be set to LinkedIn.
Example LinkedIn Response JSON
{
"identityProvider": {
"applicationConfiguration": {
"1c212e59-0d0e-6b1a-ad48-f4f92793be32": {
"createRegistration": true,
"enabled": true
}
},
"buttonText": "Login with LinkedIn",
"client_id": "86b3nbfinbhrnl",
"client_secret": "gAi3V7mC2LGzriQR",
"debug": false,
"enabled": true,
"id": "6177c09d-3f0e-4d53-9504-3600b1b23f46",
"insertInstant": 1595361142909,
"lastUpdateInstant": 1595361143101,
"name": "LinkedIn",
"scope": "r_emailaddress r_liteprofile",
"tenantConfiguration": {
"e872a880-b14f-6d62-c312-cb40f22af465": {
"limitUserLinkCount": {
"enabled": false,
"maximumLinks": 42
}
}
},
"type": "LinkedIn"
}
}Delete the LinkedIn Identity Provider
There is only one LinkedIn Identity Provider, so this Identity Provider may be deleted by type or Id.
Request
URI
?type=LinkedInURI
6177c09d-3f0e-4d53-9504-3600b1b23f46Response
This API does not return a JSON response body.
| Code | Description |
|---|---|
| 200 | The request was successful. The response will contain a JSON body. |
| 400 | The request was invalid and/or malformed. The response will contain an Errors JSON Object with the specific errors. This status will also be returned if a paid FusionAuth license is required and is not present. |
| 401 | You did not supply a valid Authorization header. The header was omitted or your API key was not valid. The response will be empty. See Authentication. |
| 404 | The object you requested doesn't exist. The response will be empty. |
| 500 | There was an internal error. A stack trace is provided and logged in the FusionAuth log files. The response will be empty. |
Complete the LinkedIn Login
This API allows you to complete a LinkedIn login after authenticating a user using the LinkedIn API. If you are using the FusionAuth login UI with the LinkedIn button you will not utilize this API directly.
This API is intended to be used if you want to build your own login page and you have added the LinkedIn login button to your own login page and you then need to complete the login with FusionAuth.
For example, if you built your own login page, you could add a "Login with LinkedIn" button and complete the LinkedIn authentication. When you complete the LinkedIn authentication you will have been returned an id token from LinkedIn. Using this API you can pass that id token to FusionAuth and we will complete the login workflow and reconcile the user to FusionAuth. The user does not need to exist yet in FusionAuth to utilize this API, depending on the configured linking strategy. The id token returned from LinkedIn will be used to retrieve the user's email address or username and if that user does not yet exist in FusionAuth the user may be created.If createRegistration has been enabled for this identity provider and the user does not yet have a registration for this application, a registration will be automatically created for the user. The user will be assigned any default roles configured for the application.
If createRegistration has not been enabled, a registration will not be created if one does not yet exist. This is useful if you wish to manually provision users and then subsequently allow them to login with LinkedIn.
Request
URI
Request Headers
The IP address of a client requesting authentication. If the IP address is provided it will be stored in the user’s login record. It is generally preferred to specify the IP address in the request body. If it is not provided in the request body this header value will be used if available. However, the request body value takes precedence.
The unique Id of the tenant used to scope this API request.
The tenant Id is not required on this request even when more than one tenant has been configured because the tenant can be identified based upon the request parameters or it is otherwise not required.
Specify a tenant Id on this request when you want to ensure the request is scoped to a specific tenant. The tenant Id may be provided through this header or by using a tenant locked API key to achieve the same result.
See Making an API request using a Tenant Id for additional information.
Request Body
code and the redirect_uri parameters to allow FusionAuth to complete this grant by exchanging the authorization code for an access_token.
redirect_uri parameter.
The unique Id of the identity provider to process this login request.
For the LinkedIn identity provider, this value will always be 6177c09d-3f0e-4d53-9504-3600b1b23f46.
X-Forwarded-For header if provided or the last proxy that sent the request. The IP address will
be stored in the User login history.
device parameter.
device parameter.
The type of device represented by the device parameter.
Prior to version 1.46.0, this value was restricted to the following types:
BROWSERDESKTOPLAPTOPMOBILEOTHERSERVERTABLETTVUNKNOWN
In version 1.46.0 and beyond, this value can be any string value you'd like, have fun with it!
When this value is set to true a JWT will not be issued as part of this request. The response body will not contain the token field, and the access_token and refresh_token cookies will not be written to the HTTP response.
This optional parameter may be helpful when performing high volume authentication requests and the JWT is not being utilized, in this scenario removing the additional latency required to issue and sign the JWT may have a measurable cumulative effect on performance.
true, if a link does not yet exist to a FusionAuth user, a 404 status code will be returned instead of using the requested linking strategy. This may be useful if you want to identify if a link exists before starting a full interactive workflow with the user to complete a link.
Example Request JSON
{
"applicationId": "10000000-0000-0002-0000-000000000001",
"data": {
"code": "ZSBxGPP9Ghyxd4QzSQeZv_MvIHuy_vBNKRVygPk_cJM",
"redirect_uri": "https://login.piedpiper.com/oauth2/callback"
},
"identityProviderId": "6177c09d-3f0e-4d53-9504-3600b1b23f46",
"ipAddress": "192.168.1.42"
}Response
The response for this API contains the User object.
Response Codes
| Code | Description |
|---|---|
| 200 | The authentication was successful. The response will contain the User object that was authenticated. |
| 202 | The user was authenticated successfully. The user is not registered for the application specified by applicationId on the request.The response will contain the User object that was authenticated. |
| 203 | The user was authenticated successfully. The user is required to change their password, the response will contain the changePasswordId to be usedon the Change Password API.Example Response JSON |
| 204 | The login is pending action by the end user. Wait and try the request again. |
| 212 | The user’s email address has not yet been verified. The response will contain the User object that was authenticated. If the verification strategy has been set to FormField, the response will contain the emailVerificationId that was generated for the user. |
| 213 | The user’s registration has not yet been verified. The response will contain the User object that was authenticated. If the verification strategy has been set to FormField, the response will contain the registrationVerificationId that was generated for the user.Prior to version 1.27.0, this status code was not returned, and you will see a 200 instead. |
| 242 | The user was authenticated successfully. The user has two factor authentication enabled. Since version 1.42.0, this status code is also returned when two factor authentication is required. The response will contain the twoFactorId to be usedon the Complete Two Factor Authentication.Example Response JSON |
| 400 | The request was invalid and/or malformed. The response will contain an Errors JSON Object with the specific errors. |
| 401 | Unable to complete the login request. The user cannot be reconciled or logged in using the external identity provider. |
| 404 | The user was not found or the password was incorrect. The response will be empty. |
| 409 | The user is currently in an action that has prevented login. The response will contain the actions that prevented login. Example Response JSON |
| 410 | The user has expired. The response will be empty. |
| 500 | There was an internal error. A stack trace is provided and logged in the FusionAuth log files. The response will be empty. |
| 503 | The search index is not available or encountered an exception so the request cannot be completed. The response will contain a JSON body. |
| 504 | One or more Webhook endpoints returned an invalid response or were unreachable. Based on the transaction configuration for this event your action cannot be completed. A stack trace is provided and logged in the FusionAuth log files. |
Response Body
Create a pending link. It will only be included in the response body when this strategy is configured and a link does not yet exist for the user. It is used in conjunction with the Link APIs to complete a pending link.A trust token that may be used to complete another API request that requires trust. For example, if you receive an error from an API indicating trust is required - indicated by this error code [TrustTokenRequired], this value can be used to satisfy the trust requirement.
True if the User is active. False if the User has been deactivated. Deactivated Users will not be able to login.
The User’s birthdate formatted as YYYY-MM-DD
The instant this user’s password was last checked to determine if it is compromised.
The unique Id of the Connector associated with the System of Record being used to authenticate the user.
This Id is used by FusionAuth when the User’s username is sent to CleanSpeak to be moderated (filtered and potentially sent to the approval queue). It is the content Id of the username inside CleanSpeak.
An object that can hold any information about the User that should be persisted.
This field will be used as the email address if no user.email field is found.
This feature was removed in version 1.26.0 and added back in in 1.27.2.
The User’s email address.
The expiration instant of the User’s account. An expired user is not permitted to login.
The first name of the User.
The User’s full name as a separate field that is not calculated from firstName and lastName.
The User’s unique Id.
The URL that points to an image file that is the User’s profile image.
The instant when the user was created.
The instant when the User logged in last.
The User’s last name.
The instant when the User was last updated.
The User’s middle name.
The User’s mobile phone number. This is useful if you will be sending push notifications or SMS messages to the User.
The email address of the user’s parent or guardian. If this value was provided during a create or update operation, this value will only remain until the child is claimed by a parent.
Indicates that the User’s password needs to be changed during their next login attempt.
The instant that the User last changed their password.
An array of locale strings that give, in order, the User’s preferred languages. These are important for email templates and other localizable text. See Locales.
The list of registrations for the User. This will include registrations for inactive applications.
The Id of the Application that this registration is for.
The Authentication Token for this registration (if one exists).
This Id is used by FusionAuth when the User’s username for this registration is sent to CleanSpeak to be moderated (filtered and potentially sent to the approval queue). It is the content Id of the username inside CleanSpeak.
An object that can hold any information about the User for this registration that should be persisted.
The Id of this registration.
The instant that this registration was created.
The instant that the User last logged into the Application for this registration.
An array of locale strings that give, in order, the User’s preferred languages for this registration. These are important for email templates and other localizable text.
The list of roles that the User has for this registration.
The User’s preferred timezone for this registration. The string will be in an IANA time zone format.
A map that contains tokens returned from identity providers.
For example, if this user has authenticated using the Facebook Identity Provider, the Facebook access token will be available in this map, keyed by name Facebook. For an OpenID Connect Identity provider, or other generic providers, if a token is stored it will be keyed by the Identity Provider unique Id.
The token returned and stored from the Identity Provider is now stored in the IdP link and is retrievable using the Identity Provider Link API.
The username of the User for this registration only. This is for display purposes and cannot be used to login.
The current status of the username. This is used if you are moderating usernames via CleanSpeak. The possible values are:
ACTIVE- the username is activePENDING- the username is pending approval/moderationREJECTED- the username was rejected during moderation
If a username has been rejected, it is still possible to allow the User to update it and have the new one moderated again.
This value indicates if this User’s registration has been verified.
For additional information, see these tutorials:
The instant that this registration was verified.
The Id of the Tenant that this User belongs to.
The User’s preferred timezone. This can be used as a default to display instants, and it is recommended that you allow Users to change this per-session. The string will be in an IANA time zone format.
The algorithm used by the TOTP authenticator. With the current implementation, this will always be HmacSHA1.
The length of code generated by the TOTP. With the current implementation, this will always be 6.
The time-step size in seconds. With the current implementation, this will always be 30.
The value of the email address for this method. Only present if user.twoFactor.methods[x].method is email.
The unique Id of the method.
true if this method was used most recently.
The type of this method. There will also be an object with the same value containing additional information about this method. The possible values are:
authenticatoremailsms
The value of the mobile phone for this method. Only present if user.twoFactor.methods[x].method is sms.
A base64 encoded secret
The User’s preferred delivery for verification codes during a two factor login request.
The possible values are:
NoneTextMessage
Determines if the User has two factor authentication enabled for their account or not.
Removed in version 1.26.0The username of the User.
The current status of the username. This is used if you are moderating usernames via CleanSpeak. The possible values are:
ACTIVE- the username is activePENDING- the username is pending approval/moderationREJECTED- the username was rejected during moderation
If a username has been rejected, it is still possible to allow the User to update it and have the new one moderated again.
Whether or not the User’s email has been verified.
For additional information, see these tutorials:
The instant that this email address was verified.
Note that this value is immutable and will only represent the first time the email was verified. If you enable re-verification on email change, this value will not change and will only represent the initial verification.
Example Response JSON
{
"token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE0ODUxNDA5ODQsImlhdCI6MTQ4NTEzNzM4NCwiaXNzIjoiYWNtZS5jb20iLCJzdWIiOiIyOWFjMGMxOC0wYjRhLTQyY2YtODJmYy0wM2Q1NzAzMThhMWQiLCJhcHBsaWNhdGlvbklkIjoiNzkxMDM3MzQtOTdhYi00ZDFhLWFmMzctZTAwNmQwNWQyOTUyIiwicm9sZXMiOltdfQ.Mp0Pcwsz5VECK11Kf2ZZNF_SMKu5CgBeLN9ZOP04kZo",
"user": {
"active": true,
"birthDate": "1976-05-30",
"connectorId": "e3306678-a53a-4964-9040-1c96f36dda72",
"data": {
"displayName": "Johnny Boy",
"favoriteColors": [
"Red",
"Blue"
]
},
"email": "example@fusionauth.io",
"expiry": 1571786483322,
"firstName": "John",
"fullName": "John Doe",
"id": "00000000-0000-0001-0000-000000000000",
"imageUrl": "http://65.media.tumblr.com/tumblr_l7dbl0MHbU1qz50x3o1_500.png",
"lastLoginInstant": 1471786483322,
"lastName": "Doe",
"middleName": "William",
"mobilePhone": "303-555-1234",
"passwordChangeRequired": false,
"passwordLastUpdateInstant": 1471786483322,
"preferredLanguages": [
"en",
"fr"
],
"registrations": [
{
"applicationId": "10000000-0000-0002-0000-000000000001",
"data": {
"displayName": "Johnny",
"favoriteSports": [
"Football",
"Basketball"
]
},
"id": "00000000-0000-0002-0000-000000000000",
"insertInstant": 1446064706250,
"lastLoginInstant": 1456064601291,
"preferredLanguages": [
"en",
"fr"
],
"roles": [
"user",
"community_helper"
],
"username": "johnny123",
"usernameStatus": "ACTIVE",
"verified": true,
"verifiedInstant": 1698772159415
}
],
"timezone": "America/Denver",
"tenantId": "f24aca2b-ce4a-4dad-951a-c9d690e71415",
"twoFactorEnabled": false,
"usernameStatus": "ACTIVE",
"username": "johnny123",
"verified": true,
"verifiedInstant": 1698772159415
}
}Response Cookies
The access token, this string is an encoded JSON Web Token (JWT). This cookie is written in the response as an HTTP Only session cookie.
The refresh token. This cookie is written in the response as an HTTP only persistent cookie. The cookie expiration is configured in the JWT configuration for the application or the global JWT configuration.