Single Sign On Authentication and using the Custom Security Param

1

Most of our systems are interconnected to our client’s systems via a single sign on pass over, so the login is handled from the client’s site and then passed to our site via various means, it all depends on what each client is using for their sign sign on handoff, some use SAML while others might pass us params via http post with a shared encryption key and algorithm to decrypt the values passed over. Any guidance on best way to integrate these different types of passed over authentications through the radzen tool?

Other similar question on security, is that on your document sample where it shows how to create the custom security.profile.country property, once a user is logged in and this property is assigned is it available to assign as a parameter from the radzen tool for the datasource calls?

Thanks,
Nick

1 Like
2

Hi Nick,

The answer to your first question is “it depends”.

Do you want to implement application level security (login, page access, user management etc) via the third party? If yes - this isn’t currently possible without a lot of custom code.

Do you want to invoke a data source method (REST API) that uses some third party security implementation? If yes - this is easier to do by injecting a service that implements the custom authentication be that HTTP header or parameter.

One can use the custom security property from the Radzen designer to invoke data source methods. It just won’t show it in the autocomplete at this time.

1 Like