Possible to mix logins with custom directory and active directory

[#1]

Hello,

was wondering if there's a way of using both active directory and custom directory connections on the same server?

We have users that are connected with Active Directory and that works fine with single sign on. Now we have a need to add some people who don't have a AD account and for that we would like to not have dynamically assigned licenses when they login and be able to hard code a username and password.

We are also using section access on the application itself with NTNAME as restrictor, would that pose a problem or is it possible to mix that as well?

Thankful for any ideas.

[Anonymous]

Привет, как поступил я:

1. Создал технологическую учетную запись в AD: User1, User2

2. Сообщил логин и пароль узкому кругу людей

3. Дал права на документ

В результате потратил одну лицензию на User(x), а народу много. Важно понимать, что одновременно имеет доступ только последний пользователь. Т.е. это подходит не для всех. Я так сделал не из-за жадности. В отделе много людей, но только один из них(по сменам), что реально анализирует. Подобных отделов много. Так удобней и дешевле

Hi, how I have done:

1. Created an account in the process AD: User1, User2

2. Reported login and password to a narrow circle of people

3. Gave rights to the document

As a result, spent one license for User (x), and a lot of people. It is important to understand that at the same time has access to only the last user. That is, it is not suitable for everyone. I did so not because of greed. In the department a lot of people, but only one of them (in shifts), which actually analyzes. Many of these departments. So it is more convenient and cheaper

[#3]

You would need to setup a separate webserver for each type of user, one for custom users and one for ntlm/AD users.

And you need to set security to DMS instead of NTFS

See attached to get a better understanding about QlikView security

[Bill_Britt]

You have to remember that authentication is not done by QlikView only authorization. So, the DMS mode would work for authorization, but the authentication would require you to build your on SSO site to do that and pass the header to QVS

Bill