Login success

Precheck Hosted page Trustdesk 4.x

Overview

The login success page is a user-friendly confirmation screen shown immediately after a user signs in. It reassures users that authentication was successful and gives them a clear next step — improving the overall experience. It is enabled per application, so each app can decide whether to show it.

When is the login success page used

When you want to confirm to the user that they successfully signed in, the login success page comes into play. In the example below, after signing in the user sees a "To the portal" action they can click to continue to their user profile portal.

Configure the login success page

1

Create the hosted page

Create a login_success hosted page with a valid URL and map it to your app's hosted page group. See Hosted Pages Management.

2

Enable the success page

In Trustdesk, go to Integrations → Applications, open your app, and open the Authentication Setup tile. Under After sign-up & sign-in, enable Success page after sign-in.

info

Success page after registration and Success page after sign-in each have their own toggle, so you can show a success screen after sign-up, after login, or both.

Understanding the flow and APIs

1

Redirect to login_success

After a successful login, the user is redirected to the login success page (hosted page key login_success). The redirect returns a track_id.

2

Continue the login

Use the track_id with the continue call to issue a token or code, depending on your grant type.

Step 1: Redirection to the login_success page

After a successful login the user is redirected to the login success page. The request looks like this:

curl `https://demo.cidaas.de/identity/login_success?track_id=5161846c-29cb-493a-8720-fc995ddd9a30&requestId=ac400efe-a58b-4d14-841c-bf17b7512a7b&sub=3b024166-2a34-4110-9f60-af4e72ee5229&q=3b024166-2a34-4110-9f60-af4e72ee5229&client_id=da6a6a31-a604-4148-afaa-84a70951230e`
 --compressed

The URL is defined by the hosted page key login_success.

It returns a track_id which is required as an input to continue the login process.

Step 2: Continue the login process

The final call issues a token or code, depending on the grant you are using. It verifies the token and grants access to the app's user profile.

curl 'https://demo.cidaas.de/login-srv/precheck/continue/958ccb4c-3985-4b17-b325-14cd10da292e' \
  -X 'POST' \
  --compressed

Developer Perspective

API	Description	Link
POST Hosted pages group	Add or update a hosted page in the specified hosted pages group.	View API
PUT Update app settings	Edit/update app details and settings. Here you can enable login_success_page. For more information, see App Management documentation.	View API
POST Continue Login	Continue the login so that a code or token is issued.	View API

Explore Related Topics

Communication Verification

Verify email or mobile as part of the login prechecks.

Claim Consent Prechecks

Collect required claim consents during login.

Suggest Verification Method

Recommend additional verification methods to the user.

---

Need help implementing this?

Please contact us on our Developer Support Page.