IBM Verify

IBM Verify

Join this online user group to communicate across Security product users and IBM experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

  • 1.  ISAM9 with Open Shift issue

    Posted 07/19/19 09:15 AM

    I have Deployed the template and spin up the pods in our internal openshift 3.7 environment.

    Even though I see the pods now running , its seems it's still running with issues…

    Issue 1) the runtime pod does not connect to config pod … On manual checking the URL only works with the –k flag ( no certs )

     

    # oc logs pod/isamruntime-3243051175-35pb7

     

    2019-07-18T01:27:55+0100: ---- Retrying....

    Error: WGAWA0662E   An invalid response code was returned from the request to https://isamconfig:9443/shared_volume/fixpacks: 403

    2019-07-18T01:28:03+0100: ---- Retrying....

    Error: WGAWA0662E   An invalid response code was returned from the request to https://isamconfig:9443/shared_volume/fixpacks: 403

    2019-07-18T01:28:10+0100: ---- Retrying....

    Error: WGAWA0662E   An invalid response code was returned from the request to https://isamconfig:9443/shared_volume/fixpacks: 403

    2019-07-18T01:28:18+0100: ---- Retrying....

    Error: WGAWA0662E   An invalid response code was returned from the request to https://isamconfig:9443/shared_volume/fixpacks: 403

    2019-07-18T01:28:27+0100: ---- Retrying....

    Error: WGAWA0662E   An invalid response code was returned from the request to https://isamconfig:9443/shared_volume/fixpacks: 403

    2019-07-18T01:28:38+0100: ---- Retrying....

    Error: WGAWA0662E   An invalid response code was returned from the request to https://isamconfig:9443/shared_volume/fixpacks: 403

    2019-07-18T01:28:49+0100: ---- Retrying....

     

    # oc rsh isamruntime-3243051175-35pb7

     

    sh-4.2$ curl -v https://isamconfig:9443/shared_volume/fixpacks

    * About to connect() to isamconfig port 9443 (#0)

    *   Trying 172.17.20.253...

    * Connected to isamconfig (172.17.20.253) port 9443 (#0)

    * Initializing NSS with certpath: sql:/etc/pki/nssdb

    *   CAfile: /etc/pki/tls/certs/ca-bundle.crt

      CApath: none

    * Server certificate:

    *       subject: CN=isamconfig-2973007414-k1dv0

    *       start date: Jul 16 23:44:54 2019 GMT

    *       expire date: Jul 16 23:44:54 2020 GMT

    *       common name: isamconfig-2973007414-k1dv0

    *       issuer: CN=isamconfig-2973007414-k1dv0

    * NSS error -8156 (SEC_ERROR_CA_CERT_INVALID)

    * Issuer certificate is invalid.

    * Closing connection 0

    curl: (60) Issuer certificate is invalid.

    More details here: http://curl.haxx.se/docs/sslcerts.html

     

    curl performs SSL certificate verification by default, using a "bundle"

    of Certificate Authority (CA) public keys (CA certs). If the default

    bundle file isn't adequate, you can specify an alternate file

    using the --cacert option.

    If this HTTPS server uses a certificate signed by a CA represented in

    the bundle, the certificate verification probably failed due to a

    problem with the certificate (it might be expired, or the name might

    not match the domain name in the URL).

    If you'd like to turn off curl's verification of the certificate, use

    the -k (or --insecure) option.

    sh-4.2$

     

     

    sh-4.2$ curl -Lvk https://isamconfig:9443/shared_volume/fixpacks

    * About to connect() to isamconfig port 9443 (#0)

    *   Trying 172.17.20.253...

    * Connected to isamconfig (172.17.20.253) port 9443 (#0)

    * Initializing NSS with certpath: sql:/etc/pki/nssdb

    * skipping SSL peer certificate verification

    * NSS: client certificate not found (nickname not specified)

    * SSL connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

    * Server certificate:

    *       subject: CN=isamconfig-2973007414-k1dv0

    *       start date: Jul 16 23:44:54 2019 GMT

    *       expire date: Jul 16 23:44:54 2020 GMT

    *       common name: isamconfig-2973007414-k1dv0

    *       issuer: CN=isamconfig-2973007414-k1dv0

    > GET /shared_volume/fixpacks HTTP/1.1

    > User-Agent: curl/7.29.0

    > Host: isamconfig:9443

    > Accept: */*

    >

    < HTTP/1.1 302 Found

    < Location: https://isamconfig:9443/core/login

    < Content-Language: en-US

    < Set-Cookie: WASReqURL=https://:9443/shared_volume/fixpacks; Path=/; Secure; HttpOnly

    < Transfer-Encoding: chunked

    < Date: Thu, 18 Jul 2019 09:20:36 GMT

    < Expires: Thu, 01 Dec 1994 16:00:00 GMT

    < Cache-Control: no-cache="set-cookie, set-cookie2"

    <

    * Ignoring the response-body

    * Connection #0 to host isamconfig left intact

    * Issue another request to this URL: 'https://isamconfig:9443/core/login'

    * Found bundle for host isamconfig: 0xb6bee0

    * Re-using existing connection! (#0) with host isamconfig

    * Connected to isamconfig (172.17.20.253) port 9443 (#0)

    > GET /core/login HTTP/1.1

    > User-Agent: curl/7.29.0

    > Host: isamconfig:9443

    > Accept: */*

    >

    < HTTP/1.1 200 OK

    < X-FRAME-OPTIONS: SAMEORIGIN

    < Cache-Control: no-cache, no-store

    < Content-Security-Policy: default-src 'self' 'unsafe-inline' 'unsafe-eval'

    < X-Content-Type-Options: nosniff

    < X-XSS-Protection: 1; mode=block

    < Strict-Transport-Security: max-age=16070400; includeSubDomains

    < Pragma: no-cache

    < Content-Type: text/html;charset=utf-8

    < Content-Language: en-US

    < Set-Cookie: JSESSIONID=0000gJWTe1Ef-J9iABwMFIeJaAR:969cff36-5992-4f29-aa2e-60222dc40746; Path=/; Secure; HttpOnly

    < Transfer-Encoding: chunked

    < Date: Thu, 18 Jul 2019 09:20:37 GMT

    < Expires: Thu, 01 Dec 1994 16:00:00 GMT

    <

    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

    <!-- IBM Confidential

      Object Code Only Source Materials

      5725-L52

      (c) Copyright International Business Machines Corp. 2012, 2016

      The source code for this program is not published or otherwise divested

      of its trade secrets, irrespective of what has been deposited with the

      U.S. Copyright Office. -->

    <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang='en' dir="ltr">

      <head>

        <meta http-equiv="Content-Type"   content="text/html; charset=UTF-8" />

        <meta http-equiv="pragma"         content="no-cache"/>

        <meta http-equiv="cache-control"  content="no-cache"/>

        <meta name="screen_id" content="Login::get" />

     

        <link rel="icon"          href="/images/favicon.ico" type="image/x-icon" />

        <link rel="shortcut icon" href="/images/favicon.ico" type="image/x-icon" />

     

        <meta name="csrf-param" content="authenticity_token"/>

        <meta name="csrf-token" content=""/>

     

     

        <meta name="cctxt" content=""/>

        <title>IBM Security Access Manager</title>

     

        <!-- ISAM CSS -->

        <link rel="stylesheet" type="text/css" href="/javascripts/dojo/dijit/themes/claro/claro.css" />

    .

    .

    .

    .

    .

    .

     

    Issue 2 ) The openldap pod is continuously getting completed followed by crashing

     

    # oc get pods

    NAME                           READY     STATUS    RESTARTS   AGE

    isamconfig-2973007414-k1dv0    1/1       Running   16         11h

    isamruntime-3243051175-35pb7   0/1       Running   0          11h

    isamwrprp1-682827843-2k6wz     0/1       Running   0          11h

    openldap-2629205293-8vzr0      1/1       Running   4          4m

    postgresql-3938822541-dzdj4    1/1       Running   0          4m

     

     

    # oc get pods

    NAME                           READY     STATUS      RESTARTS   AGE

    isamconfig-2973007414-k1dv0    1/1       Running     16         11h

    isamruntime-3243051175-35pb7   0/1       Running     0          11h

    isamwrprp1-682827843-2k6wz     0/1       Running     0          11h

    openldap-2629205293-8vzr0      0/1       Completed   4          4m

    postgresql-3938822541-dzdj4    1/1       Running     0          4m

     

    # oc get pods

    NAME                           READY     STATUS             RESTARTS   AGE

    isamconfig-2973007414-k1dv0    1/1       Running            16         11h

    isamruntime-3243051175-35pb7   0/1       Running            0          11h

    isamwrprp1-682827843-2k6wz     0/1       Running            0          11h

    openldap-2629205293-8vzr0      0/1       CrashLoopBackOff   4          4m

    postgresql-3938822541-dzdj4    1/1       Running            0          5m



    ------------------------------
    Mayur Wattamwar
    ------------------------------


  • 2.  RE: ISAM9 with Open Shift issue

    Posted 07/19/19 09:43 AM
    Edited by Jon Harry 07/19/19 09:47 AM
    Mayur,

    If you have just installed Access Manager then you will see this 403 error from the runtime/dsc/reverse proxy nodes because the username/password they are trying to use for authentication to the configuration container is not valid.  My demo assets are hardcoded to use username cfgsvc and password Passw0rd.  If you login to LMI and set the password for cfgsvc user to Passw0rd then that should fix 403.

    This is covered by my cookbook (https://ibm.biz/isamkubecookbook section 5.5) although more general rather than OpenShift.

    For the OpenLDAP container issue I don't have enough information to comment.  You do need to have a security constraint which allows run-as-root for the OpenLDAP container - perhaps that is causing an issue?   You could do an oc describe pods <openldap pod> or an oc logs <openldap pod> to see if there is any information there on the failure?

    Jon.

    ------------------------------
    Jon Harry
    Consulting IT Security Specialist
    IBM
    ------------------------------



  • 3.  RE: ISAM9 with Open Shift issue

    Posted 07/22/19 03:36 AM
    can you give me your demo link? i will check and get back to you.

    ------------------------------
    Mayur Wattamwar
    ------------------------------



  • 4.  RE: ISAM9 with Open Shift issue

    Posted 07/22/19 06:05 AM
    Mayur,

    My github repo for the scripts I've created is at https://ibm.biz/isamdocker
    I assumed this was where you got the "template" you mentioned... is there something else?

    My "ISAM on Docker" build blogs are:
    https://ibm.biz/isamdockerbuild
    https://ibm.biz/isamkubebuild

    These set up a system where you can run cookbooks:
    https://ibm.biz/isamdockercookbook
    https://ibm.biz/isamkubecookbook
    https://ibm.biz/isamhelmcookbook

    I don't have a cookbook for OpenShift - however, if you run the docker and kubernetes cookbooks you'll get a good understanding of what is needed to set up with OpenShift using the scripts assets in my Github repo.

    Cheers... Jon.

    ------------------------------
    Jon Harry
    Consulting IT Security Specialist
    IBM
    ------------------------------

    Original Message


  • 5.  RE: ISAM9 with Open Shift issue

    Posted 07/24/19 01:33 AM
    Hi Jon,

    I have now got the ISAM part running ..
    So we can now get the ISAM console and see and change configuration.

    Although I am not yet sue if they are rightly started or not.

    Considering the runtime and wrprp container still shows 0/1 Running , I would expect it to show 1/1 running

     

    /# oc get pods

    NAME                           READY     STATUS             RESTARTS   AGE

    isamconfig-2973007414-0wsjv    1/1       Running            77         2d

    isamruntime-3243051175-58j6d   0/1       Running            0          2h

    isamwrprp1-682827843-9fdjm     0/1       Running            0          2h

    openldap-2629205293-xx2pc      0/1       ImagePullBackOff   0          1d

    postgresql-3938822541-79t92    1/1       Running            0          1d

    can you check following logs to confirm that this is the expected behaviour or not

    Logs are as below.

    # oc logs -f isamwrprp1-682827843-9fdjm

    2019-07-23T11:43:28+0000: Bootstrapping....

    2019-07-23T11:43:32+0000: ---- Log files for this container will be written to docker-fd8a7

    / /

    /

    2019-07-23T11:43:32+0000: ---- Creating path: /var/application.logs/docker-fd8a7/lmi

    2019-07-23T11:43:32+0000: ---- Creating path: /var/application.logs/docker-fd8a7/rsyslog_forwarder

    2019-07-23T11:43:32+0000: ---- Creating path: /var/application.logs/docker-fd8a7/isam_runtime/policy

    2019-07-23T11:43:32+0000: ---- Creating path: /var/application.logs/docker-fd8a7/isam_runtime/user_registry

    2019-07-23T11:43:32+0000: ---- Creating path: /var/application.logs/docker-fd8a7/wrp

    2019-07-23T11:43:32+0000: ---- Creating path: /var/application.logs/docker-fd8a7/system

    2019-07-23T11:43:34+0000: ---- Creating path: /var/shared/snapshots

    2019-07-23T11:43:34+0000: ---- Creating path: /var/shared/support

    2019-07-23T11:43:34+0000: ---- Creating path: /var/shared/fixpacks

    2019-07-23T11:43:34+0000: ---- Creating path: /var/shared/extensions

    Docker detected

    2019-07-23T12:43:36+0100: ---- Downloading data from the configuration service.

    2019-07-23T12:43:59+0100: ---- Data has been downloaded from the configuration service.

    MAC verified OK

    MAC verified OK

     

    Verifying checksums... Done

    Fatal error: WGAWA0022E   The supplied instance name, rp1, is not a configured instance.

    2019-07-23T12:44:22+0100: --- Running.

    2019-07-23T12:44:41+0100: Log file: /var/log/messages

    Jul 23 12:44:20 mesa_config[530]: Fatal error: WGAWA0022E   The supplied instance name, rp1, is not a configured instance.

    Jul 23 12:44:21 mesa_config[530]: LMI:Lite. Starting the App Server

    Jul 23 12:44:21 mesa_config[530]: XML Schema for [/etc/policies//cml/common/sysaccount/sysaccount2_0_0.xml] validate passed

    Jul 23 12:44:21 mesa_control[520]: Bootstrap from settings succeeded

    Jul 23 12:44:21 mesa_control[520]: GLGSY0015I:: GLG_events:: ||

    Jul 23 12:44:21 mesa_control[520]: Bootstrap succeeded

    Jul 23 12:44:21 wga_notifications: WGAWA0047W:: WGA_events:: |1=rp1,msg=Reverse Proxy is not running: rp1|

    Jul 23 12:44:22 mesa_config[608]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 12:44:22 mesa_control[520]: Policy changes have been kept.

    Jul 23 12:44:29 mesa_config[651]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 12:45:21 mesa_config[806]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 12:50:28 mesa_config[1597]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 12:55:16 mesa_config[2318]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 13:00:35 mesa_config[3099]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 13:05:16 mesa_config[3782]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 13:10:06 mesa_config[4450]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 13:15:24 mesa_config[5242]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 13:20:06 mesa_config[5943]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 13:25:19 mesa_config[6724]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 13:30:16 mesa_config[7478]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 13:35:18 mesa_config[8242]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 13:40:23 mesa_config[9013]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 13:45:08 mesa_config[9717]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 13:50:33 mesa_config[10529]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 13:55:08 mesa_config[11217]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 14:00:19 mesa_config[11997]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 14:05:13 mesa_config[12736]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 14:10:38 mesa_config[13476]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 14:15:15 mesa_config[14158]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 14:20:28 mesa_config[14937]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 14:25:16 mesa_config[15655]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 14:30:33 mesa_config[16430]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 14:35:20 mesa_config[17096]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 14:40:30 mesa_config[17841]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 14:45:15 mesa_config[18500]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 14:50:08 mesa_config[19184]: Signature verification passed for file: /usr/sbin/mesa_config

     

     

     

     

    # oc logs -f isamruntime-3243051175-58j6d

    2019-07-23T11:42:09+0000: Bootstrapping....

    2019-07-23T11:42:13+0000: ---- Log files for this container will be written to docker-c1206

    / /

    /

    2019-07-23T11:42:13+0000: ---- Creating path: /var/application.logs/docker-c1206/lmi

    2019-07-23T11:42:13+0000: ---- Creating path: /var/application.logs/docker-c1206/rsyslog_forwarder

    2019-07-23T11:42:13+0000: ---- Creating path: /var/application.logs/docker-c1206/rtprofile

    2019-07-23T11:42:13+0000: ---- Creating path: /var/application.logs/docker-c1206/rtaudit

    2019-07-23T11:42:13+0000: ---- Creating path: /var/application.logs/docker-c1206/system

    2019-07-23T11:42:15+0000: ---- Creating path: /var/shared/snapshots

    2019-07-23T11:42:15+0000: ---- Creating path: /var/shared/support

    2019-07-23T11:42:15+0000: ---- Creating path: /var/shared/fixpacks

    2019-07-23T11:42:15+0000: ---- Creating path: /var/shared/extensions

    Docker detected

    2019-07-23T12:42:18+0100: ---- Downloading data from the configuration service.

    2019-07-23T12:42:31+0100: ---- Data has been downloaded from the configuration service.

    MAC verified OK

    MAC verified OK

     

    Verifying checksums... Done

    2019-07-23T12:42:54+0100: --- Running.

    2019-07-23T12:43:13+0100: Log file: /var/log/messages

    Jul 23 12:42:51 mesa_config[509]: LMI:Lite. Starting the App Server

    Jul 23 12:42:53 rsyslogd:  [origin software="rsyslogd" swVersion="8.24.0-34.el7" x-pid="571" x-info="http://www.rsyslog.com"] start

    Jul 23 12:42:53 mesa_config[509]: XML Schema for [/etc/policies//cml/common/sysaccount/sysaccount2_0_0.xml] validate passed

    Jul 23 12:42:53 mesa_control[496]: Bootstrap from settings succeeded

    Jul 23 12:42:53 mesa_control[496]: GLGSY0015I:: GLG_events:: ||

    Jul 23 12:42:53 mesa_control[496]: Bootstrap succeeded

    Jul 23 12:42:54 rsyslogd: rsyslogd's userid changed to 6000

    Jul 23 12:42:54 mesa_config[582]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 12:42:54 mesa_control[496]: Policy changes have been kept.

    Jul 23 12:43:01 mesa_config[617]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 12:45:20 mesa_config[961]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 12:50:20 mesa_config[1633]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 12:55:16 mesa_config[2286]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 13:00:35 mesa_config[2951]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 13:05:15 mesa_config[3548]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 13:10:09 mesa_config[4125]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 13:15:22 mesa_config[4795]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 13:20:07 mesa_config[5412]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 13:25:19 mesa_config[6091]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 13:30:17 mesa_config[6758]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 13:35:17 mesa_config[7418]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 13:40:23 mesa_config[8076]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 13:45:10 mesa_config[8704]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 13:50:32 mesa_config[9397]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 13:55:12 mesa_config[10007]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 14:00:21 mesa_config[10668]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 14:05:13 mesa_config[11306]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 14:10:02 mesa_config[11873]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 14:15:01 mesa_config[12498]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 14:20:29 mesa_config[13196]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 14:25:08 mesa_config[13816]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 14:30:02 mesa_config[14444]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 14:35:20 mesa_config[15076]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 14:40:30 mesa_config[15707]: Signature verification passed for file: /usr/sbin/mesa_config

    Jul 23 14:45:15 mesa_config[16287]: Signature verification passed for file: /usr/sbin/mesa_config




    ------------------------------
    Mayur Wattamwar
    ------------------------------

    Original Message


  • 6.  RE: ISAM9 with Open Shift issue

    Posted 07/24/19 06:16 AM

    Mayur,

    The behavior you are seeing is expected.  The "worker containers" (i.e. AAC Runtime, Rerverse Proxy, DSC) will not fully start until they receive a configuration from the config container that they can use to start and run.

    I can see from the message:

     Fatal error: WGAWA0022E   The supplied instance name, rp1, is not a configured instance.
    that you have not completed Reverse Proxy configuration and I guess you haven't done any configuration yet (other than set the password for cfgsvc).

    Now that you have access to the configuration interface, I suggest that you follow the steps in the Docker Cookbook which will set up a basic configuration for the environment.  Once this is complete and published your other containers should fully start.

    I notice that your openldap container is showing an ImagePullBackoff.  I'm not sure why that would be - there's nothing special about that image that would prevent it from downloading.  Running that image under OpenShift does require a special security constraint to allow run-as-root but hopefully you already got that from the Github scripts.

    Jon.

    ------------------------------
    Jon Harry
    Consulting IT Security Specialist
    IBM
    ------------------------------

    Original Message


  • 7.  RE: ISAM9 with Open Shift issue

    Posted 08/05/19 05:57 AM
    Edited by Mayur Wattamwar 08/05/19 05:59 AM
    John,
    I got the LMI access and was trying to configure the postgres and ldap but having the issue while using the IP of the server or container.

    do you have any document where I can start configuration? 

    ------------------------------
    Mayur Wattamwar
    ------------------------------

    Original Message


  • 8.  RE: ISAM9 with Open Shift issue

    Posted 08/05/19 06:07 AM
    Mayur,

    I would suggest that you review the Docker cookbook.  This starts from basics of Native Docker installation and use of Access Manager in containerized environment.  https://ibm.biz/isamdockercookbook.

    Once you have done this, you might also like to follow the Kubernetes cookbook to get familiar with deployment in a Kubernetes managed environment. https://ibm.biz/isamkubecookbook.

    Once you have completed these two cookbooks, I think you will have a better understanding of the ISAM-on-Docker concepts to allow you to get everything working under OpenShift.

    Jon.

    ------------------------------
    Jon Harry
    Consulting IT Security Specialist
    IBM
    ------------------------------

    Original Message


Related Content