suneet_shah

[suneet_shah]

Hi Deep
If you are looking at end-user access, then you only to make 443 and 80 available.
Depending on the systems you need to integrate, the ports will vary. For example, communication from RabbitMQ to the AD connector is on port 5672. If you are connecting to LDAP its going to 389 or 636.

If you can share more details, we can guide you better.

[suneet_shah]

Hi Gregory
You are missing the search filter in your managed system configuration.
We will try to publish a tutorial for this later this week

[suneet_shah]

Hi Arvind

The IPA connector can be downloaded from https://download.openiam.com/release/community/4.2.0.7/connectors/ipa-connector-rabbitmq.jar

We will publish docs this week

[suneet_shah]

We will be publishing an example with OpenLDAP this week

[suneet_shah]

IPA connector can be downloaded from
https://download.openiam.com/release/community/4.2.0.7/connectors/ipa-connector-rabbitmq.jar

We have not published external-facing docs yet. I will try to shortly.

[suneet_shah]

Hi Deivid,

Do you see any error messages in the UI logs?
Can try to access the application over port 8080? This will bypass the webserver/rProxy and we can see if the problem is coming from the webserver. It’s possible that apache is not automatically restarting.

[suneet_shah]

Hi Gregory,

The TLS connections related to RabbitMQ are only supported in the Enterprise edition.

[suneet_shah]

You shouldnt have to wait 1 hour for the services to come up. Normal time is between 10-15 min depending on the environment. The screenshot ofthe services not does not help. Can you post your logs form the ESB? Can you check if the RabbitMQ, Redis and Elasticsearch are running?

[suneet_shah]

Hi Arvind,
Can you post the logs from the ldap connector?
Please also post the ldap connector managed system configuration (blank out anything that is sensistive)

[suneet_shah]

Glad to hear that you are up and running

[suneet_shah]

Hi Tamilselvan

Problem seems to be with the vault
See this message
>> main] org.openiam.vault.VaultConfigResolver : Can’t talk to vault

By any chance, did you forget to run the generate_cert.sh script which sets up the vault?

[suneet_shah]

Hi Arvind,
We will be posting a video for this later this week. Have you already done the following?
a) Start the ldap connector
b) Create a managed system
c) Associated the managed system role to test the provisioning?

[suneet_shah]

Hi Tamilselvan,

Are the infrastructure components running?
– Redis, Rabbit, Elastisearch?

Can you post the logs for the ESB?

[suneet_shah]

Hi Gregory,

To enable HTTPS, you should follow the steps described here

https://docs.openiam.com/docs-4.2.0.7/installation/2-docker-installation/1-https

You need to another layer on top of OpenIAM to enable https.

[suneet_shah]

Hi Jayesh,

You can find details to unlock the account here
https://docs.openiam.com/docs-4.2.0.7/installation/2-docker-installation/3-faq-docker

The last two digits are zeros.

Can you check the esb logs to see if there any errors being thrown?

[Author]

Posts