[SHIRO-337] adding support for CDI

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.0, 1.2.1
• Fix Version/s: 2.0.0-alpha
• Component/s: Integration: JEE
• Labels: patch patch-with-test
• Assignee: Lenny Primak
• Reporter: Romain Manni-Bucau
• Created: 05/Jan/12 14:02
• Updated: 06/Feb/23 20:27
• Resolved: 06/Feb/23 20:27

Description

As there is a spring or guice integration, a CDI integration could be welcomed.

Features:

• enable shiro components to be injectables (subject, session, security manager) - Done
• (superceeded/merged) make interceptors for Shiro annotations (similar/duplicate of SHIRO-898)
• Make CDI beans available in shiro.ini - Done
• enable shiro to be configurable via cdi beans (producer methods) instead of shiro.ini (not being done, users can do their own initialization easier and better via existing APIs, than the proposed methods)
• Async / "reactive" support (not being done, due to Project Loom superseding this)

Issue Links

• Is contained by: SHIRO-897 Group all Jakarta-EE related issues here
• is depended upon by: SHIRO-422 Reference CDI Managed Beans from INI files
• is depended upon by: SHIRO-39 JEE integration
• is duplicated by: SHIRO-26 JBoss 4.x and 5.x initial support
• is superceded by: SHIRO-898 Migrate Jakarta EE support from FlowLogix to Shiro
• supercedes: SHIRO-422 Reference CDI Managed Beans from INI files
• links to: GitHub Pull Request #24
• links to: GitHub Pull Request #24
• links to: GitHub Pull Request #56
• links to: GitHub Pull Request #58
• links to: GitHub Pull Request #58
• links to: GitHub Pull Request #695