nagyesta/assumed-identity repository overview

This is a simple test double simulating how Azure Instance MetaData Service is handling Managed Identity Tokens. If the Docker artifact is started on 169.254.169.254, the locally executed tests can keep using the same authentication method as in case of the production code (assuming that the production code is using Managed Identity tokens).

⁠Usage

⁠Starting the container (on a developer machine)

Assumed Identity must use the 169.254.169.254 IP in order to simulate the real Managed Identity mechanism with the fake token provider. To achieve this you need to first create an appropriate network with Docker.

# One time setup
docker network create --subnet=169.254.169.0/24 assumed-id

Then you need to make sure to use the right IP when running the container.

docker run --net assumed-id --ip 169.254.169.254 --rm nagyesta/assumed-identity:<version>

Please find the list of available versions here⁠.

Once the container is started, you can test it by navigating to http://169.254.169.254/metadata/identity/oauth2/token?api-version=2018-02-01&resource=https://localhost/⁠

It should respond with a token similar to this:

{"access_token":"dummy","expires_in":172800,"expires_on":1693250639,"refresh_token":"dummy","resource":"https://localhost/","token_type":"Bearer"}

⁠Starting the container (on a cloud hosted VM)

The default configuration (as detailed in the usage section) does not work on cloud VMs because they are using the 169.254.169.254 IP for the real service providing instance metadata. As a workaround, you can simply start the Assumed Identity container with the default, automatically assigned IP and configure it to use a non-default port. For example by using the following command:

docker run -e ASSUMED_ID_PORT=8080 -p 8080:8080 --rm nagyesta/assumed-identity:<version>

Please find the list of available versions here⁠.

Once the container is started, you can test it by navigating to http://localhost:8080/metadata/identity/oauth2/token?api-version=2018-02-01&resource=https://localhost/⁠

It should respond with a token similar to this:

{"access_token":"dummy","expires_in":172800,"expires_on":1693250639,"refresh_token":"dummy","resource":"https://localhost/","token_type":"Bearer"}

When you have verified that your Assumed Identity instance is working as expected, you can configure the tested application to use it by adding the appropriate environment variables depending on the language and the client implementation. These are specifically mentioned in the Lowkey Vault examples here⁠.

⁠Git repository

For more information please visit the repository on GitHub⁠!