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
mk-oracle: use the ASM credentials when connecting to an ASM instance
The `asm_*` fields were parsed but never read, so ASM instances were
contacted with the regular database credentials.
`Target::connection_auth()` now picks the `asm_*` values for ASM
targets and the regular ones for everything else; the per-field
fallbacks are unchanged, so a config without `asm_*` behaves as
before. The wallet setup is decided per target too, so
`asm_type: wallet` works with standard database credentials.
CMK-37729
Change-Id: I14084b1633dcd7e8d357bdcc6b2463c1a162add1
asm_username: 'asm_user' # optional, only used for ASM instances
170
+
asm_password: 'asm_pass' # optional, only used for ASM instances
171
+
asm_role: 'sysasm' # optional, only used for ASM instances
172
+
asm_type: 'standard' # optional, only used for ASM instances
169
173
```
170
174
171
175
Set `type: wallet` to use Oracle Wallet authentication instead of username/password (see [Oracle Wallet Authentication](#oracle-wallet-authentication) below).
172
176
177
+
#### ASM Authentication
178
+
179
+
ASM instances (a SID or instance name starting with `+`, e.g. `+ASM`) are usually
180
+
reached with different credentials than a normal database. The `asm_*` fields
181
+
hold those credentials and replace their regular counterparts whenever the plugin
182
+
connects to an ASM instance; normal database connections ignore them. This
183
+
mirrors `ASMUSER` of the legacy `mk_oracle` plugin.
184
+
185
+
Each field falls back to its regular counterpart when it is not set:
0 commit comments