Skip to content

Conversation

@developerzohaib786
Copy link
Contributor

Fixes #98

Make the OAuth token URL configurable via VITE_OAUTH_TOKEN_URL environment variable to support integration with 3rd party providers like Keycloak.

Changes:

  • Use config.OAUTH_TOKEN_URL in auth.ts with fallback to default
  • Document VITE_OAUTH_TOKEN_URL in . env.example and README. md
  • Add Keycloak integration example and configuration guide
  • Update Dockerfile to include VITE_OAUTH_TOKEN_URL environment variable
  • Support both build-time and runtime configuration

Defaults to '/api/catalog/v1/oauth/tokens' for backward compatibility.

Fixes apache#98

Make the OAuth token URL configurable via VITE_OAUTH_TOKEN_URL environment
variable to support integration with 3rd party providers like Keycloak.

Changes:
- Use config.OAUTH_TOKEN_URL in auth.ts with fallback to default
- Document VITE_OAUTH_TOKEN_URL in . env.example and README. md
- Add Keycloak integration example and configuration guide
- Update Dockerfile to include VITE_OAUTH_TOKEN_URL environment variable
- Support both build-time and runtime configuration

Defaults to '/api/catalog/v1/oauth/tokens' for backward compatibility.

See: https://github.com/jbonofre/polaris-tools/tree/keycloak-support
@dimas-b dimas-b requested a review from jbonofre January 21, 2026 15:41
Copy link
Contributor

@binarycat0 binarycat0 left a comment

Choose a reason for hiding this comment

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

Thanks for the contribution and for taking the time to work on this PR — it’s appreciated.

I noticed that this change includes several updates that seem unrelated or redundant with respect to the main purpose of the PR. To help keep reviews focused and maintainable, could you please reduce the scope to only the changes strictly required for the intended fix/feature?

Since this repository is maintained under the Apache Polaris community, we also try to follow the Apache contribution guidelines closely. In particular, it would be great if you could align this PR with the code contribution guidelines described here:
https://polaris.apache.org/community/contributing-guidelines/#code-contribution-guidelines

Narrowing the changeset and following these guidelines will make it much easier for the community to review and merge the contribution.

Thanks again for your effort, and please let us know if anything in the guidelines is unclear.

# or more contributor license agreements. See the NOTICE file
# distributed with this work for additional information
# regarding copyright ownership. The ASF licenses this file
# regarding copyright ownership. The ASF licenses this file
Copy link
Contributor

Choose a reason for hiding this comment

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

Extra whitespace?

# KIND, either express or implied. See the License for the
# specific language governing permissions and limitations
# under the License.
# under the License.
Copy link
Contributor

Choose a reason for hiding this comment

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

Extra whitespace


# Build stage
FROM registry.access.redhat.com/ubi9/nodejs-22-minimal:9.7-1767673763 AS builder
FROM node:22-slim AS builder
Copy link
Contributor

Choose a reason for hiding this comment

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

AFAIK this image was used in purpose.
Please check this PR - 34e63e6


# Copy package files
COPY package.json ./
COPY package. json ./
Copy link
Contributor

Choose a reason for hiding this comment

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

Extra whitespace

@developerzohaib786
Copy link
Contributor Author

Thanks for the contribution and for taking the time to work on this PR — it’s appreciated.

I noticed that this change includes several updates that seem unrelated or redundant with respect to the main purpose of the PR. To help keep reviews focused and maintainable, could you please reduce the scope to only the changes strictly required for the intended fix/feature?

Since this repository is maintained under the Apache Polaris community, we also try to follow the Apache contribution guidelines closely. In particular, it would be great if you could align this PR with the code contribution guidelines described here: https://polaris.apache.org/community/contributing-guidelines/#code-contribution-guidelines

Narrowing the changeset and following these guidelines will make it much easier for the community to review and merge the contribution.

Thanks again for your effort, and please let us know if anything in the guidelines is unclear.

if i am not wrong please confirm that i have to Revert to Red Hat UBI image??

@binarycat0
Copy link
Contributor

if i am not wrong please confirm that i have to Revert to Red Hat UBI image??

I consider this change as not meeting the main purpose of this PR.
However, if you have concerns of using Red Hat UBI image it's better to open additional PR/Discussion issue.

Besides that please review your changes, it contains many additional whitespaces and non ASCII chars, all around the codebase.

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.

Console: Be able to configure the token URL

4 participants