-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated the "Generate the workflows package" section in the readme related to a support ticket #391
base: dev
Are you sure you want to change the base?
Conversation
README.md
Outdated
For authentication, you need a Client ID and Client Secret of this service account. | ||
|
||
If you have both values, the API key is just base64($clientid:$clientSecret). For | ||
base64 you can use a tool in our Portal: https://portal.axinom.com/mosaic/tools/base64 | ||
(or any other base64 tool). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
something like this makes sense?
If you already have the plaintext Client ID
& the Client Secret
of the service account, you can generate the base64($clientid:$clientSecret)
to be used as the api-key
using a tool BASE64 generator tool, such as: https://portal.axinom.com/mosaic/tools/base64
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
README.md
Outdated
Please note, that you need to provide the 'Base64 Encoded Credentials' of a | ||
service account that has the `Pilets: Publish` permissions as `api-key`. This | ||
[service account](https://docs.axinom.com/platform/core/identity/authenticate-serviceaccount/#what-is-a-service-account) | ||
that has the `Pilets: Publish` permissions under the "Micro Frontend Service" as `api-key`. This |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
slightly change to something like this?
Please note, that you need to provide the Base64 Encoded Credentials of a
service account as the value of api-key
. This service account must contain the Pilets: Publish
permission of the "Micro Frontend Service" in order to be authorized to perform the action of publishing the workflows.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
README.md
Outdated
value will be shown to you alongside with the other secrets when creating a | ||
service account or when generating new secrets for an existing account. | ||
|
||
For authentication, you need a Client ID and Client Secret of this service account. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should either be removed, or moved further up.
As this is the general info, that the call needs the service account details - and then we can explain which permissions it needs and how to obtain it:
- on creation we show the calculate value
- if you have the plaintext values already, you can use the base64 tool, etc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
Pull Request
Prerequisites
dev
for features andmaster
forreleases)
Description