Password Change Management for Oracle Database with TK Exception Template in senhasegura

When performing a password change for an Oracle database using the TK Exception template in senhasegura, it is important to understand how the port and connectivity configuration influences the process. Below, we provide a detailed guide on how senhasegura handles the port variable during template execution and how to proceed in cases of multiple connectivities.

How ​​the Port Variable Works in the TK Exception Template:

  1. Collecting the Port During Execution:
  • The PORT variable in the template does not use a static value, such as the default port 1521. Instead, it collects the information directly from the connectivity configured on the device in senhasegura. This approach ensures that the correct port is used according to the specific device configuration.
  1. Port Selection for Multiple Connectivities:
  • If the device has multiple connectivities configured, such as ORACLE:1521 and ORACLE:900, senhasegura automatically chooses the first listed connectivity, which in the example would be port 1521.

Scenario with Multiple Ports:

  • Example: If a device has ports 1521 and 1522 configured and both appear in the connectivities, senhasegura will select the port that appears first in the registration order to perform the password change. If it is necessary to use different ports, you can register different devices.

Password Change for User ‘sys’:

  • Given that the user ‘sys’ connects with a specific string “as sysdba”, and senhasegura does not implement the connection in this way in the default template, it is necessary to use an authentication credential with elevated privileges to change the password for this user.