[ https://issues.jboss.org/browse/SRAMP-531?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on SRAMP-531:
-----------------------------------
https://developer.jboss.org/message/910780
> Consider moving ZipToSrampArchiveRegistry/ZipToSrampArchive use server-side
> ---------------------------------------------------------------------------
>
> Key: SRAMP-531
> URL: https://issues.jboss.org/browse/SRAMP-531
> Project: S-RAMP
> Issue Type: Enhancement
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> Currently, artifacts are expanded w/ ZipToSrampArchiveRegistry/ZipToSrampArchive in multiple locations client-side. See:
> - shell's UploadArtifactCommand and DeployCommand
> - ui's ArtifactUploadServlet
> - wagon's SrampWagon
> - server's Maven facade (MavenRepositoryServiceImpl)
> Consider moving the expansion somewhere central and server-side.
> If the concern was that it's not spec-compliant, consider moving the expanders out of the atom module and create something isolated.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
[ https://issues.jboss.org/browse/RTGOV-609?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-609:
-----------------------------
Git Pull Request: https://github.com/Governance/rtgov/pull/233
> Use KeyCloak for SSO support
> ----------------------------
>
> Key: RTGOV-609
> URL: https://issues.jboss.org/browse/RTGOV-609
> Project: RTGov (Run Time Governance)
> Issue Type: Task
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.1.0.Final
>
>
> Overlord currently implements its own SSO mechanism using PicketLink.
> KeyCloak (http://keycloak.jboss.org/) provides a more general SSO solution that has user management UIs and support for social logins. Other jboss projects will also be moving over to use it - so it makes more sense to switch to using this project for SSO support.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
[ https://issues.jboss.org/browse/RTGOV-609?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-609.
------------------------------
Resolution: Done
> Use KeyCloak for SSO support
> ----------------------------
>
> Key: RTGOV-609
> URL: https://issues.jboss.org/browse/RTGOV-609
> Project: RTGov (Run Time Governance)
> Issue Type: Task
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.1.0.Final
>
>
> Overlord currently implements its own SSO mechanism using PicketLink.
> KeyCloak (http://keycloak.jboss.org/) provides a more general SSO solution that has user management UIs and support for social logins. Other jboss projects will also be moving over to use it - so it makes more sense to switch to using this project for SSO support.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
[ https://issues.jboss.org/browse/RTGOV-621?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-621:
-----------------------------
Git Pull Request: https://github.com/Governance/rtgov/pull/232
> Install using embedded ant
> --------------------------
>
> Key: RTGOV-621
> URL: https://issues.jboss.org/browse/RTGOV-621
> Project: RTGov (Run Time Governance)
> Issue Type: Task
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.1.0.Final
>
>
> Use an embedded instance of ant as the basis for the install, to remove dependency on having ant installed (for benefit of docker image size).
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)