Skip to content

Conversation

@binarycat0
Copy link
Contributor

@binarycat0 binarycat0 commented Jan 23, 2026

Motivation

The previous configuration approach required environment variables for each Polaris instance, which doesn't align with the concept of a management console that can connect to multiple Polaris environments. This created inflexibility when experimenting with different Polaris deployments and authentication methods.

This work is a preparation before introduce OIDC integration with Console UI: [WIP] #125

Features

  • Users can now configure multiple workspaces, each with its own Polaris server, realm, and authentication settings
  • Workspaces are managed through UI instead of environment variables
  • Each workspace can have different auth providers (currently supports client credentials, with OIDC support unblocked for future implementation)

Benefits

  • Connect to multiple Polaris instances from a single console
  • Switch between environments without reconfiguration
  • Experiment with different authentication methods per workspace
  • Unblocks future OIDC authentication implementation
  • Better UX with workspace management UI and session persistence

Additional Details

  • Removed environment variable dependency for realm/auth configuration
  • Added workspace selector on login page
  • Each workspace defines: server URL, realm, realm header name, and auth providers

Minors

  • Bringing make format util command

cc: @jbonofre @sohanhonavar @adam-christian-software @dimas-b


Modified login form

image

Ability to chose between the multiple workspaces and auth methods

image

Dummy warning about WIP on the OIDC implementation

image

Workspaces Management space

image

Show active worskpace. Switching between workspaces

image

@dimas-b dimas-b requested a review from jbonofre January 23, 2026 17:35
Copy link

@dimas-b dimas-b left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very nice improvement, @binarycat0 ! I think this feature is worth adding to Polaris UI.

I cannot say much about actual code change, but I ran this UI in my local and it worked very well. Some UX notes below.

  • In the "create workspace" there are auto-filled values, but I do not see an easy way to accept them... the Create button does not work unless I type in the same values manually.
  • When under Home it's not clear what workspace I'm in. Current Realm is shown, though, but it's not 1:1 with workspace.
  • Workspaces show all possible workspaces, but on the left-hand pane this page is parallel to Catalogs, while Catalogs is specific to the current workspace, I assume, right? This is kind of awkward. I'd proposed to remove the Workspaces page from the left-hand pane and only show the current workspace when the user is logged in.

@binarycat0
Copy link
Contributor Author

Very nice improvement, @binarycat0 ! I think this feature is worth adding to Polaris UI.

I cannot say much about actual code change, but I ran this UI in my local and it worked very well. Some UX notes below.

* In the "create workspace" there are auto-filled values, but I do not see an easy way to accept them... the `Create` button does not work unless I type in the same values manually.

* When under Home it's not clear what workspace I'm in. Current Realm is shown, though, but it's not 1:1 with workspace.

* `Workspaces` show all possible workspaces, but on the left-hand pane this page is parallel to `Catalogs`, while `Catalogs` is specific to the current workspace, I assume, right? This is kind of awkward. I'd proposed to remove the `Workspaces` page from the left-hand pane and only show the current workspace when the user is logged in.

Hello! Thanks for the interesting findings and your experience, it's very valuable.
It's totally worth to populate the default values in the form's fields for new entries, so I will think how to manage this.

Yeah, I'm agree about workspaces, it's really not obvious which is active and how to switch between them and if it's available even. I have a couple ideas how to manage this, I will give it a try.

@binarycat0 binarycat0 marked this pull request as draft January 23, 2026 23:28
@binarycat0
Copy link
Contributor Author

During my work on this PR I introduce "prettier" linting tool and then later I decided to move linting-changes as separate PR.
Depends on: #139

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants