[MGNLSSO-244] Make CustomAthorizationGenerator configurable (custom properties) Created: 21/Mar/23 Updated: 18/Apr/23 |
|
| Status: | Selected |
| Project: | Single Sign On |
| Component/s: | None |
| Affects Version/s: | 3.1.0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Carlos Cantalapiedra | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||
| Epic Link: | SSO maintenance | ||||
| Story Points: | 8 | ||||
| Work Started: | |||||
| Description |
|
For including custom properties at a custom AuthorizationGenerator (as we have for groups or fixedRoles) you have to override the Pac4jProvider class which also dependes on lots of other classes (SSoConfig, SSoMpConfig, SSoLoginFilter...). Would be nice to find a way to just by yaml be able to load custom properties, e.g: config.yaml
authorizationGenerators:
- name: customAuthorizationGeneratorProvider
myProperties:
mappings:
- name: customName
targetProperties:
- property1
- property2
Which are mapped at the Generator so you can use them. |