Use this guide when the user already has a Neuro account or Legal Identity. Do not create a duplicate identity merely to establish an application session.
Login and cross-Neuron behavior differ by deployment. Use only the login flow and redirect behavior confirmed by the target Neuron’s operator.
Start here
Workflow choices
Application responsibilities
- Bind the Neuro session to the correct application user.
- Let the user select the Legal Identity used for the application workflow.
- Keep JWTs and session cookies out of URLs and logs.
- Handle rejection, expiry, cancellation, and remote-Neuron failure.
- End both the application session and Neuro session as required by the product’s logout policy.
Test cancellation, expiry, logout, and remote-Neuron failure on the deployment before enabling the flow for users. 
