ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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
Goal: Use d3.json to fetch JSON data from an API that requires a scoped bearer token for least‑privilege access, while ensuring that expired credentials are handled without exposing the token to unrelated parts of the application. Constraint: d3.json (and related loaders) accept only a URL and an optional callback, and they internally call fetch(url) or XMLH
SSH Agent Forwarding allows a client to use local private keys for authentication on a remote server, enabling subsequent jumps to other hosts without storing sensitive keys on intermediate servers. This mechanism relies on the creation of a Unix domain socket on the remote host to communicate back to the local ssh-agent. While this simplifies multi-hop work
Signature Algorithm Deprecation OpenSSH 8.8 and later versions have disabled the ssh-rsa signature algorithm by default. This change targets the use of SHA-1 for signatures during the authentication handshake, though the underlying RSA key pair remains valid if a more secure signature scheme is employed. Compatibility Constraints Systems maintaining legacy c
The goal is to understand whether Contao can return a distinct, user‑friendly message when a backend user’s LDAP credentials are marked as expired, rather than the generic "Invalid username or password" response it currently provides. Contao does not implement native password expiration for backend accounts and relies on external authentication sources to en
When integrating with the Sketch REST API, authentication is managed via an API token passed in the Authorization header. While requests missing a token consistently return a 401 Unauthorized response, there is uncertainty regarding the API's behavior when a token is syntactically valid but lacks the necessary permissions for a specific resource. The goal is
I'm using postgresql and as part of learning, I tried to change to login methods to have a more secure login methods. e.g. using scram-sha-256 instead of md5 . I tried to change my password_encryption to scram-sha256 in postgresql.conf file, and changed pg_hba.conf METHOD to scram-sha-256 as well, you can see the changes in the configuration below: # - Authe
Implementing a least-privilege security model in Apache Cassandra typically involves configuring the PasswordAuthenticator and utilizing GRANT / REVOKE commands to restrict access to specific keyspaces and tables. While Cassandra supports granular Role-Based Access Control (RBAC), the internal authentication provider does not natively support automated crede
Node-RED Admin API /flows Endpoint Permission Check When the adminAuth setting is disabled, the /flows endpoint does not perform an explicit permission verification, allowing unauthenticated requests to read or modify flows. Deployments triggered through this endpoint may fail silently, and the log only shows a generic “Error: Failed to deploy flow” message
Asked · 28 Dec 2023, 08:22 UTC
answered · 31 Dec 2023, 08:22 UTC
d3js
ssh
contao
postgresql
cassandra