Is there a way to use LDAP/Active Directory for user authentication on WebLog Expert?

Avatar
Aaron Newark
  • updated
  • Answered
Is there a way with the web interface to tie users from Active Directory/LDAP for user accounts so we don't have separate user management with separate passwords to manage?
active directory ldap user management users web interface
Replies 10
Avatar
0
Michael
Quote from Aaron Newark
Thanks for the reply, but was curious, couldn't we change the line below in the web.config and tie the site to a security group in the allow/deny rules in IIS? Like doing the following:

From This

To This:
Support for Windows authentication has been added in version 9.5 beta 1, it can be downloaded from https://www.weblogexpert.com/download...
Avatar
0
Michael
Support for Windows authentication has been added in version 9.5 beta 1, it can be downloaded from https://www.weblogexpert.com/download...
Avatar
0
Michael
Quote from Aaron Newark
Thanks for the reply, but was curious, couldn't we change the line below in the web.config and tie the site to a security group in the allow/deny rules in IIS? Like doing the following:

From This

To This:
This feature is planned, but unfortunately we cannot provide a specific time frame for it.
Avatar
0
Sanket gupta
Quote from Aaron Newark
Thanks for the reply, but was curious, couldn't we change the line below in the web.config and tie the site to a security group in the allow/deny rules in IIS? Like doing the following:

From This

To This:
any update on when this feature might be available.
Avatar
0
Michael
Unfortunately the reports doesn't support authentication via Active Directory/LDAP.

However, please note that there is a way to use special links that include username and password and give it to users, so they will be able to access reports without need to enter username and password manually. For example: http://127.0.0.1:9991/Login.aspx?username=user&password=pwdhttp://127.0.0.1:9991/Login.aspx?ReturnUrl=/Report.aspx?id=1&username=user&password=pwd
Avatar
0
Michael
Quote from Aaron Newark
Thanks for the reply, but was curious, couldn't we change the line below in the web.config and tie the site to a security group in the allow/deny rules in IIS? Like doing the following:

From This

To This:
We'll consider adding this feature, thank you.
Avatar
0
Aaron Newark
Quote from Aaron Newark
Thanks for the reply, but was curious, couldn't we change the line below in the web.config and tie the site to a security group in the allow/deny rules in IIS? Like doing the following:

From This

To This:
The only problem is this leads to more management of users, would love an active directory or LDAP tie in for creating user accounts. The way we're using it is for developers who manage apps on all profiles. It stinks we have to manage another user account process but I understand. Any way I can request this feature in for a new/future build?
Avatar
0
Michael
Quote from Aaron Newark
Thanks for the reply, but was curious, couldn't we change the line below in the web.config and tie the site to a security group in the allow/deny rules in IIS? Like doing the following:

From This

To This:
It shouldn't work as the reports check which profiles can be viewed by logged user. And in any case such configuration would only allow you to simplify access to all reports, not per-profile access, and you can also do it by using the link with username and password shown in my answer.
Avatar
0
Aaron Newark
Quote from Aaron Newark
Thanks for the reply, but was curious, couldn't we change the line below in the web.config and tie the site to a security group in the allow/deny rules in IIS? Like doing the following:

From This

To This:
Sorry the code was stripped out because I forgot the proper tags.

From this

<authentication mode="Forms">
<forms name="ASPXWLEWEBAPP" loginUrl="Login.aspx" protection="All" path="/" timeout="30" defaultUrl="Default.aspx" />
</authentication>

To This:

<authorization>
<allow roles="DomainName\WindowsGroup" />
<deny users="*" />
</authorization>
Avatar
0
Aaron Newark
Thanks for the reply, but was curious, couldn't we change the line below in the web.config and tie the site to a security group in the allow/deny rules in IIS? Like doing the following:

From This

To This:

Customer support portal powered by UserEcho