Authentication
Sign-in, password reset and change, session guards and interceptors, and the principal store.
Every mode a Sinequa application signs a user in with — credentials, SSO, OAuth, SAML, bearer — funnels
through the same handful of pieces: a guard that protects routes, an interceptor that carries the session on
the HttpClient channel, and four views AuthPageComponent switches between.
What's next
Sign In
The credentials form, and the entry point of the whole authentication sequence.
Authentication flows
How the guard, the interceptor, sign-in and logout fit together end to end.
AuthGuard
Protects routes, and redirects to change-password when the session's password has expired.
Principal store
The signed-in user's data, loaded once and shared through a signal store.
Auth interceptor
Carries the session on the Angular HttpClient channel, which the atomic client never sees.
Change Password
Current/new/confirm, then signs the user back in — standalone or embedded.
Forgot Password
A one-field reset-email request, safe to embed anywhere.
Signed Out
The post-logout confirmation that breaks the external-mode re-authentication loop.
Getting started
Install @sinequa/atomic-angular, connect a client, sign a user in, and render a first authenticated search screen with a facet.
Sign In
Render the credentials form or drive the SSO/OAuth/SAML/bearer handshake automatically, with declarative Signal Forms validation and safe post-login navigation.