Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix issues in QSG and GDPR-QSG to support IS 5.7.0 API changes #79

Merged
merged 7 commits into from
Aug 8, 2018
Merged

Fix issues in QSG and GDPR-QSG to support IS 5.7.0 API changes #79

merged 7 commits into from
Aug 8, 2018

Conversation

GDRDABARERA
Copy link
Contributor

Purpose

QSG and GDPR-QSG didn't work with IS 5.7.0 giving Unauthorized User error.

echo "| Before run this make sure your WSO2 IS and Tomcat is running |"
echo "| in default ports WSO2 IS - localhost:9443 |"
echo "| tomcat - localhost:8080 |"
echo "| Next, Try the below steps in order |"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shall we have above part edited as below?

echo "| Before running this, make sure your WSO2 IS and Tomcat is     |"
echo "| running in default ports.                                     |"
echo "|        WSO2 IS - localhost:9443                               |"
echo "|        tomcat  - localhost:8080                               |"
echo "| Next, try below steps in order.                               |"

Copy link
Contributor Author

@GDRDABARERA GDRDABARERA Aug 8, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is releasing basically for IS 5.7.0, due to API changes in some admin services of IS 5.7.0, this QSG does not work for lower versions. We need to handle this issue in QSG level if not we can not compatible with all the version. Issue: #81. Let's fix this in the release

@@ -122,7 +122,7 @@
<li class="dropdown user-name">
<a href="#" class="dropdown-toggle" data-toggle="dropdown">
<img class="img-circle" height="30" width=30" src="img/Admin-icon.jpg"> <span
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like an error here with width=30"

@@ -499,6 +498,14 @@ curl -s -k -H "Authorization: Basic ${auth}" -H "Content-Type: text/xml" -H "SOA
<xsd1:permissionAndRoleConfig></xsd1:permissionAndRoleConfig>
<!--Optional:-->
<xsd1:saasApp>false</xsd1:saasApp>
<xsd1:owner>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was under the impression we were not going to use the default admin user in any of our demonstrations of the QSG

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes this should be Cameron

Copy link
Contributor Author

@GDRDABARERA GDRDABARERA Aug 7, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was initially created with the SPs registered in admin user. I fixed only the API changes. Will fix this in the next milestone release.

Copy link
Contributor Author

@GDRDABARERA GDRDABARERA Aug 7, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

An issue #80 created. This will be fixed this for the next release

@@ -24,7 +24,7 @@
<!--Optional:-->
<xsd1:applicationName>notification-center</xsd1:applicationName>
<!--Optional:-->
<xsd1:callbackUrl>http://localhost.com:8080/notification/oauth2client</xsd1:callbackUrl>
<xsd1:callbackUrl>http://localhost:8080/notification/oauth2client</xsd1:callbackUrl>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can't we configure the hotstname as a variable here? e.g. http://${host.name}:8080/notification/oauth2client and then read the actual hostname from a single file as it is hardcoded in several places?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will be fixed in next milestone #82

@GDRDABARERA GDRDABARERA merged commit 84b178d into wso2:master Aug 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants