Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug]: Custom Authentication Provider with Logoff Control Not Respecting Custom Page Layout

Open
  • Is something wrong?
#7,280 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
53/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
csharp
Domain
authentication

Research direction

Start by reproducing the issue with a custom login page and a provider whose logoff control inherits from AuthenticationLogoffBase; compare /logoff and /default.aspx?ctl=logoff with /user-login?ctl=logoff. Then trace how those URLs select and render the logoffControlSrc and the custom page layout. Done means the default logoff URLs render the control with the configured custom layout, without the reported interaction errors.

Written by the indexing model from the issue text.

Description

Status: New
Is there an existing issue for this?
  • I have searched the existing issues
What happened?

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?
  1. Create a custom authentication provider with a custom loginControlSrc and logoffControlSrc
  2. 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.
  3. 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.

Affected Versions

10.3.2 (latest release)

What browsers are you seeing the problem on?

No response

Code of Conduct
  • I agree to follow this project's Code of Conduct
Dominant language
C#
Stars
1.1k
Forks
791
Avg merge
2d 2h
Merged PRs (30d)
24

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dnnsoftware/Dnn.Platform

All issues in dnnsoftware/Dnn.Platform

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.