Our open-source "IIQ in Docker" repository has been updated

IdentityIQ (IIQ) IIQ Show and Tell
1

I’ve just updated IDW’s IIQ-in-Docker builder so that it works with the most recent versions of IIQ. I also upgraded Tomcat, MySQL, Java, and other components at the same time.

It takes about 3 minutes on my Macbook Pro to spin up a new IIQ instance with a demo HR table ready for consumption and a target table for use as a JDBC connector target.

The broader docker-compose configuration also includes a demo LDAP target, two IIQ nodes, and a load balancer.

The repository is mirrored in two locations:

3 Likes
2

Thanks @drosenbauer

This is great

3

I get ant path error while running ./build.sh

‘’’
=> Creating and cleaning build directory

=> Build directory is /Users/dheerajkumar/git/sailpoint-docker/build

The ‘ant’ executable is not available on your path"
‘’’

4

Got this Resolved, Actually ant was not installed in my Mac, so installed its and set path and it worked, posting this for others if they run into same issue:

cd ~/Downloads # Let’s get into your downloads folder.

tar -xvzf apache-ant-1.8.1-bin.tar.gz # Extract the folder

sudo mkdir -p /usr/local # Ensure that /usr/local exists

sudo cp -rf apache-ant-1.8.1-bin /usr/local/apache-ant # Copy it into /usr/local

Add the new version of Ant to current terminal session

export PATH=/usr/local/apache-ant-1.9.16/bin:“$PATH”

Add the new version of Ant to future terminal sessions

echo ‘export PATH=/usr/local/apache-ant-1.9.16/bin:”$PATH"’ >> ~/.profile

Verify new version of ant

ant -version

5

docker run --init -it -d -p8080:8080 git.identityworksllc.com:5005/idw/idw-sailpoint/sailpoint-docker:latest command gives below error:
“docker: Error response from daemon: Head “https://git.identityworksllc.com:5005/v2/idw/idw-sailpoint/sailpoint-docker/manifests/latest”: denied: access forbidden.”

6

Did your terminal paste the command with the “https://” on the front? It should be run without that.

The Docker Compose build does this:

build: ./iiq-build
image: git.identityworksllc.com:5005/idw/idw-sailpoint/sailpoint-docker:${TAG-latest}
7

Hm, no, that isn’t it. And the command as you have it above does work for me.

Maybe try adding --pull=missing to the command line. It will then error if the image isn’t available locally.

If that doesn’t work, do a docker images to list the images you have available locally. You should see an entry like this:

git.identityworksllc.com:5005/idw/idw-sailpoint/sailpoint-docker   latest            ec48d91f6b64   5 minutes ago   1.71GB
8

Hi @Davin Thanks for responding, For me issue is with Docker on my Mac M1 Machine. Docker Compose command is not working due to which build is getting failed. Now i am not getting git pull issue.

9

Sorry for the late response.

What error are you getting from docker compose? I am also using a Mac, but Intel. Docker Desktop 4.15.0, which has Docker engine 20.10.21.

10

Docker Compose is now working in my system, and looks like i am able to spin up the service as well, but how do i access sailpoint?

image
image1920×697 117 KB

i can access http://localhost:28080/dashboard/ url but not iiq:

image
image1920×1200 104 KB

11

Thank you Devin Rosenbaure,

I am able to access sailpoint over port 8080:

image
image2880×1800 142 KB

1 Like
12

Hey Dheeraj and @drosenbauer , I am also able to access http://localhost:28080/dashboard/ but not the localhost:8080. All the containers are up and running. Can you help me with the last step to access IIQ. Thanks!

14

Hi Devin,
Really nice stuff, thank you a lot for it.

I was wondering, would there be a way to achieve the same but this time with SailPoint IIQ Partners Demo (like the SERI Halifax Partner Demo Image) ?

All the best.

15

Sorry for the lengthy delay here, Amine. Here is a link directly to the part of the document that discusses SERI.

16

Hi Devin, I followed the recommended path. However, when trying to open http://localhost:8080/, it displays 404 page not found. Would you know why? Please find below screenshots of all the steps!

I tried to launch the iiq console too, but I’m getting this error:

iiq.hostname : a974b4f14a92-console
2024-03-28T21:43:37,736  WARN main springframework.context.support.ClassPathXmlApplicationContext:559 - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'versionChecker' defined in class path resource [configBeans.xml]: Invocation of init method failed; nested exception is java.lang.RuntimeException: Unable to check IdentityIQ database version: Table 'identityiq.spt_database_version' doesn't exist
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'versionChecker' defined in class path resource [configBeans.xml]: Invocation of init method failed; nested exception is java.lang.RuntimeException: Unable to check IdentityIQ database version: Table 'identityiq.spt_database_version' doesn't exist

image
image1685×982 180 KB

image
image1190×984 181 KB

image
image1601×676 105 KB

image

17

@AmineS @aishwaryagoswami
I got same issue. Are you solve this issue ? can you give me some guide about this issue ?

19

I think “localhost:8080” error comes from database setup failure.

So I could access “localhost:8080” successfully after reconstruct database.

I had reconstruct mysql database not using rather than default db setting mssql.

Summary :

  1. Reconstruct Database
  2. Import init.xml
  3. iiq container stop and start
  4. wait some long time until can see frontends 2 instances on traefik dashboard (28080 port)
20

Hi guys. I just pushed an update that should fix both of your issues.