[MGNLSSO-71] Provide uninstallation instructions Created: 16/Jul/21  Updated: 03/Aug/22

Status: Open
Project: Single Sign On
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Maxime Michel Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File dev-prod.png     PNG File install-message.png    
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: SSO support for custom IdPs
Team: AdminX

 Description   

Because the module updates the filter chain and makes the instance rely on an external server, it can be hard to uninstall the module. Instructions should therefore be provided.



 Comments   
Comment by Richard Gange [ 16/Jul/21 ]

I think the module needs two modes. dev and prod. in dev mode the sso filter is disabled and the old login filter is still in place. dev is the default mode.

Comment by Edwin Guilbert [ 16/Jul/21 ]

I agree with rgange's approach. That would get rid of the need of the "mock server" in many cases and also provides a way of soft uninstalling it, just by disabling it (dev mode). I guess the mode should be configured in magnolia properties so its outside of the running state.

Comment by Richard Gange [ 16/Jul/21 ]

Put SSO filter in front of Basic filter. Create a custom bypass called isDevMode. Configure it on both filters and "not" it for Basic filter.

Comment by Richard Gange [ 16/Jul/21 ]

I take that back you don't even need a custom class for this:

Just install it this way if magnolia.sso.mode != 'prod'

Comment by Richard Gange [ 16/Jul/21 ]

And then something like this:

Comment by Lucas Belcher [ 11/Jan/22 ]

Hi @rgange, I found this ticket while looking for a way to do this myself. Was the above a working example of how to disable sso for dev mode?

Generated at Mon Feb 12 10:50:50 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.