OIDC or Local User Auth not passed to New_Dashboard

Bug #2066944 reported by Brandt Freidank
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Landscape Server
Status tracked in Beta
23.10
Fix Released
Critical
Mitch Burton
24.04
Fix Released
Critical
Mitch Burton
Beta
Fix Released
High
Mitch Burton

Bug Description

After fresh install of Landscape 24.04 on Ubuntu 24.04 new authentication prompt produced after clicking Repositories link to navigate to new_dashboard page.

If local users are used the authentication works as expected but expect passthrough of login from initial page to new_dashboard page.

If OIDC authentication is configured in /etc/landscape/service.conf and Repositories link is clicked user is prompted for login which does accept OIDC credentials. Trying local account credential initially created during initial configuration on the second login prompt after clicking the repositories page does not work.

Expect configured authentication method in /etc/landscape/service.conf to pass through and be utilized throughout Landscape.

information type: Proprietary → Public Security
information type: Public Security → Private Security
information type: Private Security → Public
Revision history for this message
Mitch Burton (mitchburton) wrote (last edit ):

Fixed in 24.04.2+1 beta. Will update when released to stable.

Changed in landscape:
status: New → Fix Committed
assignee: nobody → Mitch Burton (mitchburton)
Revision history for this message
Mitch Burton (mitchburton) wrote :

There is a minor workaround right now:
  1. log in to the old dashboard
  2. go to /settings
  3. generate or regenerate your API credentials
  4. go back to /account/standalone

Then your session should carry over to the new_dashboard

Changed in landscape:
importance: Undecided → High
Revision history for this message
Philipp Neuhaus (philippunims) wrote :

This workaround or updating did non work for me:

I manually installed 24.04..

After some debugging I found that a "secret_token" was missing in my service.conf under [landscape]:

Adding
secret-token = [random 32 Byte char]

did the work.

I am not sure if is a second bug or connected....

Revision history for this message
Mitch Burton (mitchburton) wrote :

The secret-token is generated by the landscape-server-quickstart package or by the landscape-server charm during installation.

If you did a manual installation, it may be missing. I think this is a probably a documentation gap that should be filled.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.