Using Single sign on (SSO) via JSON web tokens

Hello

I'm updating a custom application to take advantage of using the SSO via Json web tokens as outlined here:

I've setup a landing page so it calls the following url: https://"school name".myschoolapp.com/app/sso/auth/"custom name ". So far so good; using Chrome (and in incognito mode), when i type in https://"school name".myschoolapp.com/app/sso/auth/"custom name“ it goes to https://”school name".myschoolapp.com/app/external#login, where the user is prompted to authenticate.

For the Redirect Url, I set it to https://www."Our Third Party App Domain".com/path?sso_token={token}. From my understanding this the Url the user will go to when successfully logged in.

My question is:
I am able to log in successfully when presented the Blackbaud sign in page at https://”school name".myschoolapp.com/app/external#login. However, after i successfully login, I do not go directly to the Redirect Url of https://www."Our Third Party App Domain".com/path?sso_token={token}. Instead, I go to the Blackbaud Resource page where the resource tiles are located (I'll need to create SSO link to a resource board). My question is, is this the correct behavior in that after successfully logging in I am directed to the Blackbaud Resource page versus being redirected to the custom application located at https://www."Our Third Party App Domain".com/path?sso_token={token}?

To me, the setup looks correct but I'm not sure if after successful login it automatically goes to the custom app or if i need to create a resource page.

Thanks

Tagged:

Comments

  • Forgot to add.
    After I've successfully logged in, shouldn't I be able to type in the redirect url and go directly to the custom app? But when I do, it keeps looping me back to the Blackbaud resource page where it has all of our resource tiles.

  • Bryna Gleich
    Bryna Gleich Blackbaud Employee
    Tenth Anniversary Kudos 3 Name Dropper Participant

    @Gail Dolormente You're currently posting in the community for the Legacy ON API.

    If this is a new application, we recommend all new development use SKY API instead of the Legacy ON API. If this is an updated application, consider migrating it to SKY API when possible. The SKY API user community is more active than the Legacy ON API as well.

    SKY API Help:

    SKY API community:

    (The link in your original post refers to SKY content, not Legacy ON API content. So I want to confirm which API you plan to use and need assistance with.)

    Help for the Legacy ON API is at


Categories