Action is required for a remote floating license server after an upgrade to version 6.0 Author: Jazz Foundation Repository team

Action is required for a remote floating license server after an upgrade to version 6.0 Author: Jazz Foundation Repository team Last updated: 27 May 2015

Mon, 22 Jun 2015

4 min read

Workaround: Action is required for a remote floating license server after an upgrade to version 6.0

Workaround summary

Action is required for a remote floating license server after an upgrade to version 6.0
Author: Jazz Foundation Repository team
Last updated: 27 May 2015

Problem

If you use a remote floating license server, and either Jazz Team Server or the license server is upgraded to version 6.0, you must complete additional steps after the upgrade.

Note: In rare cases, you might experience license-related issues after an upgrade to version 6.0 if you use a local floating license server. In those cases, do not follow these instructions. Instead, modify the floating license server URL as the error message instructs you to.

Workarounds

Depending on your scenario, complete one of the following workarounds.

Workaround 1: Jazz Team Server is upgraded to version 6.0

If you upgrade Jazz Team Server to version 6.0, you might need to establish a friend relationship between the Jazz Team Server and the floating license server. If this situation occurs, you see the CRJAZ2916E message on the status summary page when you restart Jazz Team Server after the upgrade. This error prevents the server from checking out any floating licenses.

CRJAZ2916E message

In this scenario, create a friend relationship between the floating license server and Jazz Team Server by completing the following steps:

On Jazz Team Server, navigate to the Friends administrative page by clicking the Friends (Outbound) link on the left of the Status Summary page.
To add the floating license server to the friends list, click Add.
In the wizard, enter a descriptive name, such as Floating license server.
Enter the root services URI for the license server, such as https://fls.mydomain.com:9443/jts/rootservices, and click Next.
On the Add Friend page, specify an OAuth secret, ensure that the Trusted check box is selected, and click Create Friend.
After the operation succeeds, click Next and then click Finish.
Log in to the floating license server as an administrator.
Navigate to the Consumers administrative page by clicking the Consumers (Inbound) link on the left of the Status Summary page.
Beside the generated provisional key, enter a consumer name to identify the Jazz Team Server, set the Authorized column to Approved, and click Save.
Refresh the page, and locate the new consumer in the Authorized Keys section.
Hover the cursor over the new row in the table until the Pencil icon is displayed; then, click the icon.
In the Edit Consumer Key Properties dialog box, in the Functional User ID field, click Select User and add a functional user such as etl_user.
In the Edit Consumer Key Properties dialog box, click Finish.
On Jazz Team Server, refresh the administrative UI and confirm that you no longer see the CRJAZ2916E message.

Workaround 2: The floating license server is upgraded to 6.0, but Jazz Team Server is not

If you upgraded the floating license server to version 6.0, but did not upgrade Jazz Team Server, you see the CRJAZ1267I message instead. In this scenario, complete the following steps:

On the floating license server, log in to the administrative UI.
Navigate to the Advanced Properties page by clicking the Advanced Properties link on the left of the Status Summary page.
Find the “Allow unauthenticated access to the floating license server” property, and set its value to true.
At the top of the page, click Save.
On Jazz Team Server, refresh the administrative UI and confirm that you no longer see the CRJAZ1267I message.

Note: Because this procedure makes the floating license server vulnerable to all unauthenticated access, this solution should only be temporary. As soon as possible, upgrade Jazz Team Server to version 6.0, ensure that the "Allow unauthenticated access to the floating license server" property is set to false, and complete Workaround 1 if necessary.

Return to the top of the page

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.

Feedback

Discussion

KrishnaKanth Naik July 27, 2015 02:54:56

Is there any specific reason why this new configuration has been brought into effect? Does this reduce any amount of chatter between the JTS server and the License server?

Roberto Sanchez Herrera August 21, 2015 08:14:14

Question about step 12 of work around 1. Suppose my licensing server has the minimum required to serve licenses: it is only a JTS server without any registered application. I did not even configure data warehouse. Therefore, I do not have any functional user, not even etl_user. Does that mean my licensing server won't work? Do I need to add a functional user to the consumer key?

Karl Freburger August 24, 2015 01:45:09

This change was made to close a security vulnerability.

Karl Freburger August 25, 2015 08:12:16

To answer the other question: you will need a user to create the friend relationship. ADMIN won't work (it's special), but any other user will. However, to avoid opening a security hole, the user should be a functional user or a user that already has JazzAdmin privs.

alma veronica martinez gonzalez October 15, 2015 03:56:06

Hi, I have the following message (Sorry, it's spanish): Este servidor se ha conectado al servidor de licencias en https://XXXXX:9443/jts/. Se ha producido un error al comunicar con ese servidor de licencia: CRJAZ1267I No se ha podido recuperar la lista de licencias flotantes de "https://XXXXX:9443/jts/service/com.ibm.team.repository.service.internal.license.IFloatingLicenseService/licenses". Este servidor es un servidor de licencias flotantes (2 tipos de licencia flotante instalados). I did the "Workaround 2", but did not work, the error still persists any ideas??

Don Yang April 20, 2018 02:54:40

If there are multiple jts servers pointing to a jts as floating license server in v6.0.3(there is no etl_user here), can we add jts_user as functional user to all of fiends or it should be different users? would there be any concern for jts_user to be in multiple friends between jts servers and remote float license license(another jts)?