Project

General

Profile

Bug #3680

Allow for different authentication services in metacat configuration

Added by Michael Daigle almost 11 years ago. Updated almost 11 years ago.

Status:
Resolved
Priority:
Normal
Category:
metacat
Target version:
Start date:
11/19/2008
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
3680

Description

Right now, the metacat configuration utility authenticates against ldap. It should allow for the usage of any authentication schema.

History

#1 Updated by Matt Jones almost 11 years ago

Shouldn't the configuration utility be using the AuthInterface interface for all of its calls? That would help abstract it away from the need for a specific LDAP implementation. Maybe an additional method or two need to be added to AuthInterface to support verifying account existence?

#2 Updated by Michael Daigle almost 11 years ago

Changed the configuration authentication to use the generic AuthSession. Added the auth class to the configuration utility. Updated install/update documentation to reflect the changes.

#3 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 3680

Also available in: Atom PDF