Daniel Keir Haywood created CAUSEWAY-3519:
---------------------------------------------

             Summary: [simpleapp] once impersonated, if cause exception, and 
click on header, then cannot stop impersonating
                 Key: CAUSEWAY-3519
                 URL: https://issues.apache.org/jira/browse/CAUSEWAY-3519
             Project: Causeway
          Issue Type: Bug
          Components: Core
    Affects Versions: 2.0.0-RC1
            Reporter: Daniel Keir Haywood
            Assignee: Andi Huber
             Fix For: 2.0.0-RC2
         Attachments: image-2023-07-04-22-48-16-698.png, 
image-2023-07-04-22-53-13-114.png, image-2023-07-04-22-54-13-561.png, 
image-2023-07-04-22-57-30-095.png, image-2023-07-04-22-58-57-970.png

This one is a bit weird, and is a slightly odd sequence to trigger, but is 
reproducible.

Run up simpleapp.

Login as sven

Don't run any fixture scripts, instead just create an object 'a'.

Navigate into a's metadata, invoke "impersonate with roles":

!image-2023-07-04-22-48-16-698.png|width=451,height=164!

Select "secman-admin".

The current user will change to:

!image-2023-07-04-22-53-13-114.png|width=285,height=53!

so far, so good.

Now, as secman-admin, attempt to create a simple object also called 'a'.  This 
triggers an exception:

!image-2023-07-04-22-54-13-561.png|width=291,height=448!

Also fine.  Press 'cancel'.

Now stop impersonating:

!image-2023-07-04-22-57-30-095.png|width=286,height=314!

 

click on the icon top left to show home page:

seem still to be impersonating, and can no longer "stop impersonating":

!image-2023-07-04-22-58-57-970.png|width=277,height=287!

Logout and log back in as sven.

click on header a few times ... toggles back to impersonating.

 

~~~

I've also managed to bring up a white label generic error page, but not 
reliably.  And I also got the app into a state where it would keep showing the 
red error as an orange warning; suggesting the MessageBroker was caching still 
somehow.

However, if I don't create an exception while impersonating, then everything 
seems to behave ok.

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to