Single Sign On - One Table for All Apps

[jimarch]

I'm using SSO for each of my Apps.  So I have an Authentication for each that uses it's own table of users for that App.  We just had to change our SSO cert which meant I had to upload the new cert into each.  So that made me wonder if there is a way to have one SSO Authentication and table that would have all of the users in it for all Apps but then a separate field with the app name that they have access to.   I would need to have multiple Apps allowed for some users.  Maybe this is something that is already available and I just don't know about it.  Or maybe someone has figured out a way to handle it.  The end result would be one master SSO user table that would only require update the cert in it the next time I have to do that.  And would give a centralized user database which would be easier to maintain.

I appreciate everyone's thoughts.

[MayMusic]

So basically you need to share the member user table among apps. There needs to be another field in this table which is holding the app name. Now the authentication for each app should be based on a view which is filtered by app name field.

[DefinitelyNot31337]

Hi @jimarch,

 

Here's one way to do it. There is another easier approach to do it, but the one I'd be discussing would be better and more standard, especially if wanted to create a CMS for your UserApps. 

 

First is to design your 3 tables for your Master Authentication

UserCredentials - master table for your users which would hold their login credentials and personal information

Apps - master table for your apps which hold per-app description

UserApps - Relating table for UserCredentials and Apps which will determine which apps a user has.

 

 

As MayMusic mentioned: After creating your tables, you will need to create a View for each of your app.

Generally, each of your View will just filter userApp table based on corresponding appId field.

 

 

After the tables and views have been set-up, create an Authentication for each of your app.

1st, create a master authentication with UserApps as your DataSource (this will be your General Standalone Login Screen. More information in this link)

Next, create an Authentication object for each of your app. The DataSource would be your per-app Views.

* Note: Make sure to also cross-app login. Also, it would be great to redirect your users to your Standalone Login Screen if they are not yet logged in.

 

Hope this information helps.

 

Regards,

DN31337

 

References:

https://howto.caspio.com/tech-tips-and-articles/common-customizations/create-user-specific-redirect-after-login/

https://howto.caspio.com/getting-started/create-user-specific-redirect-after-login/

https://howto.caspio.com/authentications-and-connections/authentication/

https://howto.caspio.com/getting-started/id-services/

https://howto.caspio.com/pre-recorded-live-training/application-architecture-and-authentication/

[jimarch]

Awesome!!  Thanks for the replies.  I've been on Vacation and just got back into the office so I will have take a closer look and test these out.  I was really hoping there was a way to handle this.  Thanks,  Jim