Bug 1483418

Summary:	Missing keycloak-client-registration-cli-2.5.7.Final-redhat-2.jar from SSO71 template.
Product:	OpenShift Container Platform	Reporter:	Glenn West <gwest>
Component:	Templates	Assignee:	kconner
Status:	CLOSED UPSTREAM	QA Contact:	XiuJuan Wang <xiuwang>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.6.0	CC:	aos-bugs, bparees, jokerman, mmccomas, pweil
Target Milestone:	---
Target Release:	3.7.z
Hardware:	All
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-10-25 20:59:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Glenn West 2017-08-21 05:19:44 UTC

Description of problem:
In automation for ocp 3.6 reference architecture, the tmplate needs to auto configure
sso as the identity provider. As part of that a client must be automatically added.
kcreg.sh executed within the container provides that functionality. kcreg.sh uses
keycloak-client-registration-cli-2.5.7.Final-redhat-2.jar, which is not in the docker container. It is in the full sso71 tar ball. 

Version-Release number of selected component (if applicable):
sso 71 template on ocp 3.6

How reproducible:


Steps to Reproduce:
1.Use https://github.com/glennswest/createsso.git 
script is create_login.sh which auto creates a sso71 container on ocp 3.6
2. run create_login.sh
3. ocp rsh {podname}
4. /opt/eap/bin/kcreg.sh

Actual results:
sh-4.2$ ./kcreg.sh
Picked up JAVA_TOOL_OPTIONS: -Duser.home=/home/jboss -Duser.name=jboss
Error: Could not find or load main class org.keycloak.client.registration.cli.KcRegMain
sh-4.2$ 

Expected results:
kcreg runs, and prints header 

Additional info:

Comment 2 Glenn West 2017-10-25 08:46:20 UTC

this is signifcant major functionality that is missing in the openshift image guys.
It burens a burned a huge amount of my time, and forced me to write signficant code
that was totally un-needed with this functioanltiy.

Its a missing package in the container. 

Doc actually specifically mentions using this vs using the rest api. 
Yet the container does not have the tool. 
This makes automations really difficult and documentation misleading at best.

Comment 3 Ben Parees 2017-10-25 20:59:53 UTC

As this is not an openshift issue and the owning team tracks issues via JIRA, I am closing this bug.