It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×6,109
×5,899

question asked: Oct 17 '16, 4:38 p.m.
question was seen: 2,833 times
last updated: Dec 01 '16, 6:10 p.m.

Related questions

Getting CRJAZ1185W cannot retrieve user "ADMIN" becuase the repository is inaccessible

0
Terry Little (11●1●5) | asked Oct 17 '16, 4:38 p.m.

I have set up JAZZ on Linux.  I am using the Requirements Management (rm). I am using Websphere front end.  I have rm deployed to Websphere and I have set up authentication through RHEL Directory Services (LDAP).  When trying to log into rm from the front end (http://www-01.ibm.com/support/docview.wss?uid=swg21693277 )   I have the mapping set up on the jazz server as follows:  Go to https://IP:port/rm) I get redirected to https://IP:port/rm/web (which is the jts rm) and I no longer get prompted for my pin (doesn't check certificate).  It would appear that when they use the same port for both Websphere App and the jts/rm, the Websphere isn't even being used to connect.  I don't really see how they could both use the same IP:port ........  I set it (WC_defaulthost_secure) back to 8443 in the Websphere Application server.   Has anyone else had this same error when accessing rm?  Any suggestions as to what is causing this error?

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Donald Nong (14.5k●6●14) | answered Oct 17 '16, 9:21 p.m.
After you configure CLM, never ever change the port number without doing a server rename. Once you log on to JTS or RM, verify what the "Public URI" is, and you should use this URI only.

I have no idea why you would change the port number if there are some problems with the LDAP configuration, as they are totally unrelated.

As for the error you got, the quoted technote already states the possible causes and you should work on them. If you need further assistance, you should provide more details about your LDAP configuration.
Comments
Terry Little commented Oct 18 '16, 10:30 a.m.

It seems that my question got kinda of jumbled.  Just to clarify, I did not change the ports due to ldap.  I used the default port for CLM and never changed it.  I changed the port for the Websphere from it's default (9443) to 8443 thus keeping the CLM URL >https://<IP:8443>/rm.  As for the errors I get with ADMIN, the technote states to make sure that the attributes uid, name or mail exist in the ldap which I have verified through the mapping on the CLM.  Is there another technote that I am not seeing?

Donald Nong commented Oct 18 '16, 6:56 p.m.

For configuring LDAP in WAS, the below article would be a good starting point. It also has many links to other useful resources.
https://jazz.net/library/article/604

For the error that you got, one possible cause is that your logged user has the JazzAdmins security role, but the user ID is not in JTS (and Jazz incorrectly assumes the "ADMIN" ID).

0
permanent link
Terry Little (11●1●5) | answered Dec 01 '16, 6:10 p.m.
Update:   After re-installing, I realized that the CLM processes do not need to be started (My first time through and so I was not aware ....  newbie).  therefore, there is no problem with the ports as it is only Websphere listening on a port with the CLM applications deployed on websphere.  So, the port problem is not an issue.   Furthermore, I found that Websphere 8.5.5.0 would did not allow for IE 11 to manage users and groups. However, firefox would, so I updated the user groups and was able to get around the login problems I was having once users were in the correct groups.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.