Seguridad Oracle Cloud PaaS ADF

Cómo asegurar las Aplicaciones Web ADF Fusion en Oracle Cloud PaaS

  1. Cree un origen de datos para su base de datos de seguridad
  2. Cree un nuevo proveedor de autenticación de Sufficient SQL Authentication utilizando el origen de datos definido
  3. Use la página MyRealm->Configuration->Provider Specific para definir la configuración específica del proveedor de autenticación SQL: SELECT ENCRYPTED_USER_PASSWORD FROM KRI_USERS WHERE USER_NAME = ?
    UPDATE KRI_USERS SET ENCRYPTED_USER_PASSWORD = ? WHERE USER_NAME = ?
    SELECT USER_NAME FROM KRI_USERS WHERE USER_NAME = ?
    SELECT USER_NAME FROM KRI_USERS WHERE USER_NAME LIKE ?
    INSERT INTO KRI_USERS (USER_ID, USER_NAME, ENCRYPTED_USER_PASSWORD, DESCRIPTION, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY) VALUES (KRI_USERS_S.NEXTVAL, ? , ? , ? , SYSDATE, ‘anonymous’, SYSDATE, ‘anonymous’)
    DELETE FROM KRI_USERS WHERE USER_NAME = ?
    SELECT G_NAME FROM KRI_GROUPS WHERE G_NAME LIKE ?
    SELECT G_NAME FROM KRI_GROUPS WHERE G_NAME = ?
    INSERT INTO KRI_GROUPS (G_NAME, G_DESCRIPTION, LAST_UPDATE_DATE,CREATION_DATE, LAST_UPDATED_BY, CREATED_BY)VALUES ( ? , ? , SYSDATE,SYSDATE, ‘anonymous’, ‘anonymous’)
    DELETE FROM KRI_GROUPS WHERE G_NAME = ?
    SELECT KU.USER_NAME FROM KRI_GROUP_MEMBERS KGM, KRI_USERS KU WHERE G_NAME = ? AND KU.USER_NAME = ? AND KGM.USER_ID= KU.USER_ID
    SELECT G_NAME FROM KRI_GROUP_MEMBERS KGM, KRI_USERS KU WHERE KU.USER_NAME = ? AND KGM.USER_ID= KU.USER_ID
    SELECT KU.USER_NAME FROM KRI_GROUP_MEMBERS KGM, KRI_USERS KU WHERE KGM.G_NAME = ? AND KU.USER_NAME LIKE ? AND KGM.USER_ID= KU.USER_ID
    DELETE FROM KRI_GROUP_MEMBERS KGM WHERE EXISTS (SELECT USER_NAME FROM KRI_USERS KU WHERE KGM.USER_ID= KU.USER_ID AND KU.USER_NAME = ?) OR KGM.G_NAME = ?
    INSERT INTO kri_group_members (g_name, user_id, last_update_date, last_updated_by, creation_date, created_by) SELECT ?, user_id, SYSDATE, ‘anonymous’, SYSDATE, ‘anonymous’ FROM kri_users WHERE user_name = ?
    DELETE FROM KRI_GROUP_MEMBERS KGM WHERE G_NAME = ? AND EXISTS (SELECT USER_NAME FROM KRI_USERS KU WHERE KGM.USER_ID= KU.USER_ID AND KU.USER_NAME = ?)
    DELETE FROM KRI_GROUP_MEMBERS WHERE G_NAME = ?
    SELECT DESCRIPTION FROM KRI_USERS WHERE USER_NAME = ?
    UPDATE KRI_USERS SET DESCRIPTION = ? WHERE USER_NAME = ?
    SELECT G_DESCRIPTION FROM KRI_GROUPS WHERE G_NAME = ?
    UPDATE KRI_GROUPS SET G_DESCRIPTION = ? WHERE G_NAME = ?
  4. Programe el mantenimiento de usuarios, roles y grupos o utilice la consola de WebLogic para modificar su jazn_data
  5. Segurice la aplicación ADF utilizando el menú de aplicaciones de JDeveloper.
  6. Recuerde no desplegar jazn_data de prueba en el entorno de producción.

No es necesario hacer esto para extender las aplicaciones de Oracle Cloud SaaS como HCM Sales u otras. Todo está gestionado por el dominio de identidad y su PaaS JCS SX.

Deja un comentario

Tu dirección de correo electrónico no será publicada. Los campos obligatorios están marcados con *