Print the name of the service token in application access logs

[nimish-ks]

Is your feature request related to a problem?

Currently all service tokens are displayed as 🔑 Service token which makes it hard to trace access.

Describe the solution you'd like

1. Print the name of the actual service used to access secrets in the logs
2. Provide a link to similar to View this secret to view the service token.

Describe alternatives you've considered

Additional context

[Dhoni77]

Hi @nimish-ks I would like to work on this

[nimish-ks]

@Dhoni77 All yours! Feel free to reach out to us on slack if you need any help / additional context -- https://slack.phase.dev

[rohan-chaturvedi]

@Dhoni77 Here's some more context on implementing this:
The SecretEvent model is what we use to track CRUD changes to Secrets:

console/backend/api/models.py

Line 309 in f63640b

class SecretEvent(models.Model):

As you can see, there's a user foreign key. If this user key is null, we assume this event was created by a service token. Instead, we need to create an additional, nullable 'token' foreign key for the Service Token model:

console/backend/api/models.py

Line 243 in f63640b

class ServiceToken(models.Model):

Then, we'll need to handle the following:

• Update graphql types:

  console/backend/backend/graphene/types.py

  Line 161 in f63640b

  class SecretEventType(DjangoObjectType):

• Update the frontend queries for logs and display the token name instead of 'Service token':

  console/frontend/components/logs/SecretLogs.tsx

  Line 264 in f63640b

  {log.user ? (

• Make sure the token is logged for each type of CRUD event via the REST api:

  console/backend/api/views.py

  Line 294 in f63640b

  class SecretsView(APIView):

As Nimish, said, feel free to join our Slack if you'd like any more context or have any questions!