mod-permissions persistent storage needs to be migrated to Postgres

Description

Since we are moving away from Mongo for Folio, the Auth module suite needs to follow suit.

Currently, the Login and Permissions modules use a Mongo backend for storage. (The Authtoken module does not currently use persistent storage).

As the Auth modules are NOT currently implemented using the RAML Module Builder, it is a valid question of whether we should reimplement the Auth modules in the RMB framework, or whether we should build our own interface with the Postgres database. We'll need to evaluate the limitations of the RMB and determine if there is any required functionality in the Auth modules that would be impeded by using the RMB. (On the other hand, it is possible that any such limitations could be worthy points for extending the RMB framework itself). A third way could be to split the code so that the CRUD operations are build with the RMB, while more complex logic is managed as a separate module.

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Jakub SkoczenJanuary 24, 2017 at 1:30 PM

The mod-permissions part has been completed, a new issue will be filed for the login/logout modules.

Jakub SkoczenDecember 8, 2016 at 12:54 PM

Ok – is that something you will look into in sprint4 (this or next week), or sprint5?

Kurt NordstromDecember 7, 2016 at 1:54 PM

Yes, this is different because mod-users was built as a RMB module from the start. mod-auth was not.

Jakub SkoczenDecember 7, 2016 at 1:51 PM

Kurt, is this different from DMOD-103? Or simply about making the same changes in a different module.

Done

Details

Assignee

Reporter

Priority

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created December 7, 2016 at 1:33 PM
Updated November 12, 2018 at 2:23 PM
Resolved January 24, 2017 at 1:30 PM
TestRail: Cases
TestRail: Runs

Flag notifications