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
* account - the account which we want to connect to
86
-
* cert_file - a path to Secrets Manager rootCA file. we need it if we initialize the client in `SslVerificationMode.SELF_SIGN`
99
+
* cert_file - a path to Secrets Manager rootCA file. Required if initializing the client in `SslVerificationMode.SELF_SIGN`
87
100
or `SslVerificationMode.CA_BUNDLE` mode
88
-
* service_id - a service id for the Secrets Manager authenticator. Required when using the ldap authenticator (see below) but not when using the default `authn` authenticator.
101
+
* service_id - a service id for the Secrets Manager authenticator. Required when using an authenticator besides the default
102
+
authn (see `Create Authentication Strategy`)
89
103
* proxy_params - parameters for proxy connection. see `ProxyParams` class for more details - Optional
90
104
91
-
#### Create credentials provider
105
+
#### Create Credentials Provider
92
106
93
-
The client uses credentials provider in order to get the connection credentials before making api command. This approach
94
-
allow to keep the credentials in a safe location and provide it to the client on demand.
107
+
The client uses a credentials provider in order to fetch connection credentials before making API calls. This allows credential
108
+
storage in a safe location on the system.
95
109
96
-
We provide the user with `CredentialsProviderInterface` which can be implemented the way the user see as best
97
-
fit (`keyring` usage for example)
110
+
We provide the user with `CredentialsProviderInterface` which can be implemented to create a custom credentials provider that
111
+
best fits the use case (`keyring` for example)
98
112
99
-
We also provide the user with a simple implementation of such provider called `SimpleCredentialsProvider`. Example of
100
-
creating such provider + storing credentials:
113
+
We also provide a simple implementation called `SimpleCredentialsProvider`. Example of
114
+
creating a provider and storing credentials:
101
115
102
116
```python
103
117
from conjur_api.models import CredentialsData
104
118
from conjur_api.providers import SimpleCredentialsProvider
The client also uses an authentication strategy in order to authenticate to Secrets Manager. This approach allows us to implement different authentication strategies
115
-
(e.g. `authn`, `authn-ldap`, `authn-k8s`) and to keep the authentication logic separate from the client implementation.
131
+
#### Create Authentication Strategy
116
132
117
-
We provide the `AuthnAuthenticationStrategy` for the default Secrets Manager authenticator. Example use:
133
+
The client uses an authentication strategy in order to authenticate to Secrets Manager. This approach allows us to implement
134
+
different authentication strategies while keeping logic separate from the client implementation. Supported strategies are based
135
+
on different Secrets Manager authenticators:
136
+
- authn (default)
137
+
- authn-ldap
138
+
- authn-oidc
139
+
- authn-jwt
140
+
141
+
We provide the `AuthnAuthenticationStrategy` for the default Secrets Manager authenticator. Example usage:
118
142
119
143
```python
120
144
from conjur_api.providers import AuthnAuthenticationStrategy
0 commit comments