Skip to main content
Solved

Custom SECURITY_LOGIN_TYPE

  • June 8, 2017
  • 1 reply
  • 6 views

Documentation for SECURITY_LOGIN_TYPE in FME Server 2016 says:

"Identifies the authentication (login) method to use: database, activedirectory, or custom"

What does "custom" mean? We would like to user Active Directory AND database authentication if possible. This would allow us to create users with passwords that don't expire, unlike with Active Directory account.

Thanks

Best answer by jlutherthomas

The custom authentication mode is because at one point in the history of FME Server we allowed users to write their own security modules for authentication. This is not supported from FME Server 2017.

 

With Active Directory, only FME 2017 allows mixed-mode authentication where you can have both active directory and database users log in. Large organizations should use 2017.1 if they want to use Active Directory.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

Forum|alt.badge.img+2
  • 364 replies
  • Best Answer
  • June 14, 2017

The custom authentication mode is because at one point in the history of FME Server we allowed users to write their own security modules for authentication. This is not supported from FME Server 2017.

 

With Active Directory, only FME 2017 allows mixed-mode authentication where you can have both active directory and database users log in. Large organizations should use 2017.1 if they want to use Active Directory.