You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the call above the callContent payload will not have the secrets directly in the payload. When dealig with the payload we directly fetch the secrets from the headers.
If the result contains the secrets, we will either:
Throw and exception/forbidden return value
Obfuscate the result
Exceptions:
ConfigException if the header variable is also the title of a callContent
ConfigException if the header variable is not present
The text was updated successfully, but these errors were encountered:
The json payload is quite dangerous regarding secrets. We need to find a way to avoid passing secrets dirctly in the payload.
We can send secrets in the headers. When received they are available to the calls as values.
We also forbid the showing of these variables by chance. I.e. if the result is equal to a header we do not show it.
Rules: Header should have the prefix "IBS-"
Example:
In the call above the callContent payload will not have the secrets directly in the payload. When dealig with the payload we directly fetch the secrets from the headers.
If the result contains the secrets, we will either:
Exceptions:
ConfigException if the header variable is also the title of a callContent
ConfigException if the header variable is not present
The text was updated successfully, but these errors were encountered: