[SHIRO-798] Improvement in Shiro API

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.7.0
• Fix Version/s: 2.0.0
• Assignee: Unassigned
• Reporter: Pavel_K
• Created: 08/Nov/20 06:51
• Updated: 06/Mar/23 08:06

Description

This issue was inspired by this thread in shiro user mailing list:

I suggest:

1)To change API to open access to some top level objects, SessionManager, SessionDAO etc.
(return null if some implementation doesn’t have one of them)
2) To separate SecurityManager from SessionManager (leave only has relation).

API must be more flexible. Particularly for Shiro 2.0 that, as I understand, must support jpms. The main idea of jpms is to have a clear API and to hide implementation.

If it is necessary to make casting and get implementations to get active sessions we can conclude that is necessary to improve API.

Issue Links

• relates to: SHIRO-781 Add JPMS support