Conversation
Co-authored-by: dkrizic <1181349+dkrizic@users.noreply.github.com>
Co-authored-by: dkrizic <1181349+dkrizic@users.noreply.github.com>
Co-authored-by: dkrizic <1181349+dkrizic@users.noreply.github.com>
|
@copilot I would like to have things changed. The /service does the actual authentication. It knows username and password via environmant varialbels vom configmaps and secrets. /cli knows them as well thru own configmap and secret. The /ui asks the user for username and password. Both /cli and /service pass the username and password to /service. |
Co-authored-by: dkrizic <1181349+dkrizic@users.noreply.github.com>
Implemented the architecture you requested. Now:
Both secrets share the same password (configured via Commit: 9fe8c18 Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
|
@copilot For the CLI I want the the paramter and environment variables are called "username" or USERNAME and password or PASSWORD, only, no authentication prefix |
Co-authored-by: dkrizic <1181349+dkrizic@users.noreply.github.com>
Changed CLI to use simpler names without "authentication" prefix:
Service still uses Commit: 0e2964a Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
Authentication was non-functional due to environment variable mismatches and missing secret mounts. CLI expected
PASSWORDbut Helm providedAUTHENTICATION_PASSWORD. UI deployment lacked secret mounts entirely, preventing login.Changes
CLI alignment
USERNAMEandPASSWORD(without AUTHENTICATION_ prefix)usernameandpasswordHelm chart fixes
AUTHENTICATION_USERNAMEto service secret (previously only contained password)<release>-cli-auth) with dedicated credentials usingUSERNAMEandPASSWORDkeysAUTHENTICATION_ENABLEDto UI configmap when service auth is enabledUSERNAMEfrom CLI configmap (now sourced from secret)Architecture
Components now use dedicated secrets for proper separation of concerns with distinct naming conventions:
Service (
<release>-authsecret)AUTHENTICATION_USERNAMEandAUTHENTICATION_PASSWORDCLI (
<release>-cli-authsecret)USERNAMEandPASSWORD(simplified naming without AUTHENTICATION_ prefix)service.authentication.password)UI (no secret mount)
AUTHENTICATION_ENABLEDflag via configmapAll secrets share the same password but are managed separately with component-specific naming conventions, allowing proper credential isolation between components.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.