Login with LINE

Request

Authenticate the user using LINE login. This endpoint should be called from the user's browser. It will redirect the User Agent to the LINE IDP and redirect back to Transmit upon successful authentication. Once Transmit verifies the authentication response, the User Agent will be redirected to the redirect_uri specified in the request. This URI will now include a code parameter in the query, which will be later exchanged for a token via the /oidc/token endpoint.

Query

client_idstring, <= 150 charactersrequired

Client ID of the application requesting authentication, retrieved from the Transmit Admin Portal

Example:client_id=DgsdfhSDsdfhtSDFXCCXBVMKPws345yscv2345XCZV

redirect_uristringrequired

URI to redirect to upon completion of the IDP flow. This is the server GET endpoint used to call the token endpoint, and should accept "code" as a query parameter. This URI must also be configured as an allowed redirect URI in the Transmit Admin Portal

Example:redirect_uri=https://www.example.com/login

create_new_userboolean

Indicates if a new user should be created if no user with associated email was found. If enabled, public signups must also be configured as allowed for the application.

Default:true

Example:create_new_user=false

resourcestring

Resource URI the login is attempting to access.

require_mfaboolean

Require multi factor authentication for this authentication request.

Default:false

Example:require_mfa=true

claimsstring

A stringified object used to request additional claims in the ID token, such as roles, permissions, and other user profile data. The structure is per the OIDC Standard. For supported claims and how to request custom claims, see the ID Token Reference. Note: You should stringify the value.

Example:claims={"id_token":{"roles":null}}

statestring

An opaque string that is used to maintain state between the request and the callback. It will be added to the redirect URI as a query parameter, which should be validated by your server to protect against cross-site request forgery (CSRF) attacks

noncestring

A random value that is included in the authentication request from the client (e.g. browser) to mitigate replay attacks. It will be added to the id_token and the backend service should only accept id_tokens that include the same nonce value as the one included in the original request

org_idstring

Organization ID, used for member login in B2B scenarios

curl -i -X GET \
  'https://api.sbx.transmitsecurity.io/cis/v1/auth/line?client_id=DgsdfhSDsdfhtSDFXCCXBVMKPws345yscv2345XCZV&redirect_uri=https%3A%2F%2Fwww.example.com%2Flogin&create_new_user=false&resource=string&require_mfa=true&claims=%7B%22id_token%22%3A%7B%22roles%22%3Anull%7D%7D&state=string&nonce=string&org_id=string'

Responses

Redirect with code

Response

No content