Microservice Security

Manage the security of your microservice through its details page easily.

Grizzly API gives you the possibility to define the security of your micorservice easily and with an effcient way and this through :

For the projects with microservice API or Markup API with default security, you can configure the token management policy that will be useful when using your microservice by using this section:

These parameters are generated autamatically when the microservice is created, but you can change them by changing the security key for example, or redefining the expiration time of the token.

For the projects with microservice API or Markup API with security delegated to IAM API, the security will be displayed like this.

And you can configure the token management policy and api keys that will be useful when using your microservice by using this section:

These parameters are generated autamatically when the microservice is created, but you can change them by redefining the expiration time of the or changing the API keys (client ID and client SECRET).

When managing the endpoints of your microservice, you may need to restrict the use of endpoints according to the user’s role. So Grizzly API has thought of you, and provided you with the option to manage the roles of your microservice using this section :

2 Roles are added by default when the microservice is created : Admin and User

One of the most frequent use cases of the security part of the microservice is endpoints security.

In this example, we will secure the endpoint /products with the role admin.