If you are using the Login API (/api/login) - this does not create an SSO session.

The FusionAuth Login pages do not currently use the access_token or refresh_token cookies for session management.

If you want the SSO feature - you need to use the FusionAuth login pages. This is the strategy outlined in the 5 minute setup guide: https://fusionauth.io/docs/v1/tech/5-minute-setup-guide

We do have a feature open to switch to token based SSO so that this use case would work: https://github.com/FusionAuth/fusionauth-issues/issues/358

That message means the user is not registered for the application you’re logging into. If you create a registration for the user you’ll see Authenticated.

More on this here: https://fusionauth.io/community/forum/topic/5/can-you-limit-a-user-s-login-authentication-access-to-applications-within-a-single-tenant/2

This is not currently available.

The plan is to build out SMS templates that can localized and customized but no timelines have been determined.

@robotdan Ah, I missed that. I was looking at the response section, which had the registration. Thanks!