You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With a custom authentication provider that implements a custom logoffControlSrc file that inherits from AuthenticationLogoffBase when the site is configured with a custom user login page, DNN does not always render the control in a manner that is expected.
Steps to reproduce?
Create a custom authentication provider with a custom loginControlSrc and logoffControlSrc
Create a custom page for the login, such as "User Login," and set the default login page to that page, and set the page to a different theme so you can tell the difference.
For testing purposes, ensure that the logoffControlSrc requires a user interaction so you can visually see it
Attempt to logoff, and notice that UI is NOT shown with your custom theme, or with your provided container when you leverage any of the default urls: /logoff or /default.aspx?ctl=logoff.
If you manually construct a logoff URL such as /user-login?ctl=logoff it will work as expected.
Current Behavior
No response
Expected Behavior
No response
Relevant log output
Anything else?
Note
Additionally, when using a proper redirect, there is still an odd placement/timing behavior in how the container is rendered that results in null reference exceptions if you try to interact with any custom ode in the container.
We have used a tempoary workaround of a hard-coded logoff URL, but shouldn't have to.
Is there an existing issue for this?
What happened?
With a custom authentication provider that implements a custom
logoffControlSrcfile that inherits fromAuthenticationLogoffBasewhen the site is configured with a custom user login page, DNN does not always render the control in a manner that is expected.Steps to reproduce?
loginControlSrcandlogoffControlSrcAttempt to logoff, and notice that UI is NOT shown with your custom theme, or with your provided container when you leverage any of the default urls:
/logoffor/default.aspx?ctl=logoff.If you manually construct a logoff URL such as
/user-login?ctl=logoffit will work as expected.Current Behavior
No response
Expected Behavior
No response
Relevant log output
Anything else?
Note
Additionally, when using a proper redirect, there is still an odd placement/timing behavior in how the container is rendered that results in null reference exceptions if you try to interact with any custom ode in the container.
We have used a tempoary workaround of a hard-coded logoff URL, but shouldn't have to.
Affected Versions
10.3.2 (latest release)
What browsers are you seeing the problem on?
No response
Code of Conduct