With the latest Radzen release candidate we shipped a preview of Active Directory authentication and authorization support. Now your Radzen applications can authenticate against Active Directory!
To try it you first need to have a MS SQL or MySQL data source in your Radzen app. This is required in order for Radzen to create a server-side application. We will probably remove that requirement.
Then follow this procedure:
Open a Radzen app.
Click security at the top right.
Set Provider to Active Directory.
Enter Server (the active directory server domain name or IP), User and Password (will be used to verify AD accounts and retrieve groups). This should be any account with read access to the active directory. Radzen needs such an account because it looks as if AD anonymous access is considered a security risk.
Click Load Groups. This will retrieve all Active Directory groups so you could use them later to allow page access only to certain groups.
The application should now support Active Directory authentication. To implement authorization click the edit button next to a Radzen page and set the Access from the dropdown.
Yes, B2C is a particular version of Azure AD, we should try if it can be used even with the current Active Directory implementation.
Ignore IdentityServer … my error
This is probably not the domain server because the connection times out. You can find the address of your domain server by following the answer of this StackOverflow answer. Once you get the IP you could use it in the Server text field.
Hello, is there a similar way (similar to the top screenshot of this thread) in the latest Radzen version to filter application-access via AD-Group-Selection? It seems that it can only be done on page level...
