-
Notifications
You must be signed in to change notification settings - Fork 113
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
[MNT-24673] fix users not seen #694
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
@@ -415,6 +415,13 @@ | |||
</form> | |||
</forms> | |||
</config> | |||
|
|||
<config evaluator="string-compare" condition="Users" replace="true"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this custom config changes is required for all this xml files?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need to keep only files which are getting copied to tomcat directory inside Dockerfile which is responsible for building image, removing extra xml files
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks fine
https://hyland.atlassian.net/browse/MNT-24673
[Isssue] - After creating project of alfresco-sdk with all-in-one jar, we are not able to see users after creating users via Admin Tools
The issue was due to a property show-authorization-status set to true in share-config-custom.xml. To fix the issue, I have overrided the property to false in share-config-custom.xml file. Now it is working as expected