Project

General

Profile

Feature #392

Update setup screen to allow configuration of roles_key

Added by Luke Murphey over 12 years ago. Updated over 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
08/12/2012
Due date:
% Done:

100%


Subtasks

Task #393: Roles key Is only updated when changedClosedLuke Murphey

Task #394: Authentication script will use vendor code and attribute unless roles_key is blankClosedLuke Murphey

Task #395: Vendor code and attribute ID was parsed from the roles_keyClosedLuke Murphey

Associated revisions

Revision 46 (diff)
Added by Luke Murphey over 12 years ago

Added ability to set the roles on the setup screen by specifying the vendor code and attribute ID individually. Closes #392.

Revision 40 (diff)
Added by Luke Murphey over 12 years ago

Added ability to set the roles on the setup screen by specifying the vendor code and attribute ID individually. Closes #392.

History

#1 Updated by Luke Murphey over 12 years ago

We may want to handle Vendor ID and vendor key separately. Below are some notes on how it ought to function:

  • When entering a vendor ID or key, the roles_key will be updated only if it is effectively different. Otherwise, the role key will be reverted to blank and the vendor ID and key will be used instead.
  • The authentication script will try to use the roles_key if not blank to find the roles and will then try to use the vendor ID and key otherwise
  • If the vendor ID or key are blank, the REST handler will return the items as parsed from the roles key (if it is set)

#2 Updated by Luke Murphey over 12 years ago

  • Status changed from New to In Progress

#3 Updated by Luke Murphey over 12 years ago

Need to make sure that the auth script:

  • Ignores a roles key that is empty
  • Prints out the attributes received from the RADIUS server cleanly

#4 Updated by Luke Murphey over 12 years ago

  • Status changed from In Progress to Closed

Applied in changeset r46.

Also available in: Atom PDF