Skip to content

update docu for custom extra headers in cmemc #225

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.

Sign up for GitHub

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

Merged
seebi merged 5 commits into from
May 6, 2026
Merged

update docu for custom extra headers in cmemc #225

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
005653b
update docu for custom extra hedaers in cmemc
louiswesterheide May 4, 2026
f802f84
Merge branch 'main' into feature/cmemcCustomHeader-CMEM-7546
louiswesterheide May 4, 2026
4e68e4a
fix up documentation of header processes
louiswesterheide May 6, 2026
e2a3143
add changelog to release notes
louiswesterheide May 6, 2026
2d563fe
fix release notes
seebi May 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions ...te/cmemc-command-line-interface/configuration/file-based-configuration/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -269,3 +269,12 @@ Setting this to a PEM file allows for using private Certificate Authorities for
Please refer to [Certificate handling and SSL verification](../certificate-handling-and-ssl-verification/index.md) for more information.

This variable defaults to `$PYTHON_HOME/site-packages/certifi/cacert.pem`.


#### CMEMC_CUSTOM_HEADER_*
Comment thread
louiswesterheide marked this conversation as resolved.

Setting this allows all http requests cmemc does to use the specified custom headers as well.

The `CMEMC_CUSTOM_HEADER_` prefix gets stripped from the header, so only `*` will remain.

This variable defaults to `none`
2 changes: 2 additions & 0 deletions ...ne-interface/configuration/getting-credentials-from-external-processes/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,7 @@ In order to get credential information from an external process you need to use
- `OAUTH_PASSWORD_PROCESS`, to set up the process to get the user password when using the `password` grant type.
- `OAUTH_CLIENT_SECRET_PROCESS`, to set up the process to get the client secret when using `client_credentials` grant type .
- `OAUTH_ACCESS_TOKEN_PROCESS`, to set up the process to get the direct access token (`prefetched_token`).
- `CMEMC_CUSTOM_HEADER_*_PROCESS` to set up the process to get custom http headers if needed (the `*` needs to be replaced with the correct header name using all uppercase and `_` instead of `-`, e.g. `CMEMC_CUSTOM_HEADER_CF_ACCESS_TOKEN_PROCESS` for the `cf-access-token` header variable)

The credential executable can use the other cmemc environment keys of the configuration block for fetching the credentials (e.g. `CMEM_BASE_URI` and `OAUTH_USER`).

Expand Down Expand Up @@ -87,6 +88,7 @@ OAUTH_CLIENT_ID=cmem-service-account
OAUTH_CLIENT_SECRET_PROCESS=["getpass.sh", "parameter1", "parameter2"]
```

Note: You need to define a named connection for this to take effect. Using the `[DEFAULT]` section fallback will not execute the process.
### Example: MacOS Keychain

Here is a working example with the MacOS Keychain, which can be queried with the command line tool `security`.
Expand Down
Loading