Description

We would like to leverage IAM authentication in blockscout as username/password authentication is not the best security practice.

To enable IAM authentication, Blockscout must support accepting URL-encoded usernames. This is because certain cloud providers mandate the use of the complete IAM username for IAM authentication, and these usernames often include special characters (such as @) that must be encoded to ensure they do not interfere with the parsing of the connection URL.

Here's an example:

• IAM user: my-user@my-project.iam (GCP IAM Service Account/User)
• DB hostname: my-database-host
• database name : my-database

connection string that works perfectly fine outside of blockscout: psql postgresql://my-user%40my-project.iam@my-database-host:5000/my-database

But blockscout doesn't support all the necessary chars for this URL to work in blockscout, this would most likely need to be updated.

Unfortunately I cannot contribute but I created a PR on my fork: https://github.com/blockscout/blockscout/pull/9588/files

Thanks!

Type of the installation

Helm charts (k8s)

Type of the JSON RPC archive node

Any

Type of the chain

No response

Link to the page

No response

Steps to reproduce

No response

Backend version

v6.X

Frontend version

No response

Elixir & Erlang/OTP versions

Any

Operating system

No response

Additional information

No response