ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Credential Lifecycle Management Argo CD implements least-privilege access by mapping external identity provider groups to internal roles via RBAC policies. For OIDC-based authentication, the API server validates the exp claim on every request, resulting in an HTTP 401 response once the token expires, which necessitates a client-side re-authentication flow. S
I'm using the @azure/msal-node package in a node application to enable my users to log in using their AzureAD credentials. Logging in and acquiring session tokens works fine, but I cannot find a way to invalidate a session / log out a user - am I overlooking something obvious here? Just for context, here's how I'm getting my tokens: // msalConfig is my valid
I'm currently writing a (Server side) Blazor application that includes the default AzureAD Authentication. This works well for authenticated users - challenging on the entrance ( _Host.cshtml ) file, redirecting and then back once authenticated. I need to have a couple of pages not requiring authentication - I don't want the user being challenged and redirec
We run Qodana linters in CI and upload results to Qodana Cloud using the QODANA_TOKEN environment variable, one project token per pipeline. The token is stored as a CI secret, and I want to settle on a credential policy before rolling this out to more repositories. The trade-off I cannot resolve from the documentation alone: a long-lived project token is ope
Request Propagation in Passport.js Passport v0.5.0 formally documented the passReqToCallback option, allowing the request object to be passed as the first argument to the verify callback. While previously associated primarily with the strategy constructor, this functionality was extended to passport.authenticate to support more dynamic configurations. Config
Authentication State in Data APIs When implementing least-privilege access in React Router v6+, developers often use loaders to validate credentials before a route renders. A common design challenge arises when a loader encounters an expired token or a 401 Unauthorized response from a backend API during the pre-render phase. Handling Expired Credentials Ther
PyPI implements scoped API tokens to facilitate least-privilege access, allowing automated tools like twine to upload packages to specific projects without requiring global account credentials. This mechanism reduces the impact of a credential leak by limiting the token's scope to a subset of the user's projects. While tokens can be manually revoked via the
Credential Handling in Modern Browser Drivers Historically, Selenium WebDriver users handled HTTP Basic Authentication by embedding credentials directly into the target URL (e.g., http://user:password@host ). However, modern Chromium-based browsers have deprecated this format due to security concerns, often ignoring the credentials or blocking the request en
The goal is to confirm whether a password change for a local Portainer user, performed through the API endpoint /api/users/{id}/password, becomes effective for subsequent authentication requests without restarting the Portainer container, or whether the change only takes effect after a container restart. Current observations show that the UI appears to apply
azure
blazor
qodana
nodejs
passport
pypi
argocd