[JBoss JIRA] (RTGOV-632) Initial display of service list on EAP is empty
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-632?page=com.atlassian.jira.plugin.... ]
Gary Brown commented on RTGOV-632:
----------------------------------
Further information from keycloak tracing:
{noformat}
12:18:50,487 TRACE [org.keycloak.adapters.as7.KeycloakAuthenticatorValve] (http-localhost.localdomain/127.0.0.1:8080-2) invoke
12:18:50,487 DEBUG [org.keycloak.adapters.PreAuthActionsHandler] (http-localhost.localdomain/127.0.0.1:8080-2) adminRequest http://localhost:8080/rtgov-ui/rest/services/search
12:18:50,488 TRACE [org.keycloak.adapters.as7.KeycloakAuthenticatorValve] (http-localhost.localdomain/127.0.0.1:8080-2) *** authenticate
12:18:50,488 TRACE [org.keycloak.adapters.RequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-2) --> authenticate()
12:18:50,489 TRACE [org.keycloak.adapters.RequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-2) try bearer
12:18:50,489 TRACE [org.keycloak.adapters.RequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-2) try oauth
12:18:50,489 DEBUG [org.keycloak.adapters.OAuthRequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-2) there was no code
12:18:50,489 DEBUG [org.keycloak.adapters.OAuthRequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-2) redirecting to auth server
12:18:50,489 DEBUG [org.keycloak.adapters.OAuthRequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-2) callback uri: http://localhost:8080/rtgov-ui/rest/services/search
12:18:50,490 DEBUG [org.keycloak.adapters.OAuthRequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-2) Sending redirect to login page: http://localhost:8080/auth/realms/governance/protocol/openid-connect/logi...
12:18:50,492 TRACE [org.keycloak.adapters.as7.KeycloakAuthenticatorValve] (http-localhost.localdomain/127.0.0.1:8080-3) invoke
12:18:50,492 DEBUG [org.keycloak.adapters.PreAuthActionsHandler] (http-localhost.localdomain/127.0.0.1:8080-3) adminRequest http://localhost:8080/rtgov-ui/rest/services/applications
12:18:50,492 TRACE [org.keycloak.adapters.as7.KeycloakAuthenticatorValve] (http-localhost.localdomain/127.0.0.1:8080-3) *** authenticate
12:18:50,492 TRACE [org.keycloak.adapters.RequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-3) --> authenticate()
12:18:50,492 TRACE [org.keycloak.adapters.RequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-3) try bearer
12:18:50,492 TRACE [org.keycloak.adapters.RequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-3) try oauth
12:18:50,493 DEBUG [org.keycloak.adapters.OAuthRequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-3) there was no code
12:18:50,493 DEBUG [org.keycloak.adapters.OAuthRequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-3) redirecting to auth server
12:18:50,493 DEBUG [org.keycloak.adapters.OAuthRequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-3) callback uri: http://localhost:8080/rtgov-ui/rest/services/applications
12:18:50,493 DEBUG [org.keycloak.adapters.OAuthRequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-3) Sending redirect to login page: http://localhost:8080/auth/realms/governance/protocol/openid-connect/logi...
12:18:50,628 DEBUG [org.jboss.resteasy.core.SynchronousDispatcher] (http-localhost.localdomain/127.0.0.1:8080-3) PathInfo: /realms/governance/protocol/openid-connect/login
12:18:50,628 DEBUG [org.jboss.resteasy.core.SynchronousDispatcher] (http-localhost.localdomain/127.0.0.1:8080-2) PathInfo: /realms/governance/protocol/openid-connect/login
12:18:50,630 WARN [org.jboss.resteasy.core.ResourceLocator] (http-localhost.localdomain/127.0.0.1:8080-3) Field providers of subresource org.keycloak.protocol.oidc.OpenIDConnectService will not be injected according to spec
12:18:50,630 WARN [org.jboss.resteasy.core.ResourceLocator] (http-localhost.localdomain/127.0.0.1:8080-2) Field providers of subresource org.keycloak.protocol.oidc.OpenIDConnectService will not be injected according to spec
12:18:50,631 WARN [org.jboss.resteasy.core.ResourceLocator] (http-localhost.localdomain/127.0.0.1:8080-3) Field securityContext of subresource org.keycloak.protocol.oidc.OpenIDConnectService will not be injected according to spec
12:18:50,631 WARN [org.jboss.resteasy.core.ResourceLocator] (http-localhost.localdomain/127.0.0.1:8080-2) Field securityContext of subresource org.keycloak.protocol.oidc.OpenIDConnectService will not be injected according to spec
{noformat}
This would suggest that the token is not being carried by the browser (chrome) but then it should also cause problems on wildfly.
> Initial display of service list on EAP is empty
> -----------------------------------------------
>
> Key: RTGOV-632
> URL: https://issues.jboss.org/browse/RTGOV-632
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.1.0.Final
>
>
> When navigating to the 'Services' page initially, the list of services is empty.
> This is because the server is returning a 'Bad Request' (code 400) - but when a refresh is performed, the response is ok and shows the list of services.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years
[JBoss JIRA] (RTGOV-632) Initial display of service list on EAP is empty
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-632?page=com.atlassian.jira.plugin.... ]
Gary Brown commented on RTGOV-632:
----------------------------------
{noformat}
11:53:19,107 WARN [org.keycloak.adapters.OAuthRequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-1) state parameter invalid
11:53:19,108 WARN [org.keycloak.adapters.OAuthRequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-1) cookie: 90/32f24cad-0359-43d7-b333-4d84964c4522
11:53:19,108 WARN [org.keycloak.adapters.OAuthRequestAuthenticator] (http-localhost.localdomain/127.0.0.1:8080-1) queryParam: 89/fd66988a-e136-4502-b66d-1faa2c920112
{noformat}
> Initial display of service list on EAP is empty
> -----------------------------------------------
>
> Key: RTGOV-632
> URL: https://issues.jboss.org/browse/RTGOV-632
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.1.0.Final
>
>
> When navigating to the 'Services' page initially, the list of services is empty.
> This is because the server is returning a 'Bad Request' (code 400) - but when a refresh is performed, the response is ok and shows the list of services.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years
[JBoss JIRA] (RTGOV-633) Situation lifecycle buttons don't react properly on EAP
by Gary Brown (JIRA)
Gary Brown created RTGOV-633:
--------------------------------
Summary: Situation lifecycle buttons don't react properly on EAP
Key: RTGOV-633
URL: https://issues.jboss.org/browse/RTGOV-633
Project: RTGov (Run Time Governance)
Issue Type: Bug
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.1.0.Final
When a situation is selected, pressing the 'Assign' or other subsequent lifecycle buttons does not immediately react. They have to be pressed multiple times before they result in an action.
Its possible that the cause is the same as for RTGOV-632 (i.e. a bad request).
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years
[JBoss JIRA] (RTGOV-632) Initial display of service list on EAP is empty
by Gary Brown (JIRA)
Gary Brown created RTGOV-632:
--------------------------------
Summary: Initial display of service list on EAP is empty
Key: RTGOV-632
URL: https://issues.jboss.org/browse/RTGOV-632
Project: RTGov (Run Time Governance)
Issue Type: Bug
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.1.0.Final
When navigating to the 'Services' page initially, the list of services is empty.
This is because the server is returning a 'Bad Request' (code 400) - but when a refresh is performed, the response is ok and shows the list of services.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years
[JBoss JIRA] (SRAMP-16) Eclipse IDE: S-RAMP tooling
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-16?page=com.atlassian.jira.plugin.s... ]
Brett Meyer commented on SRAMP-16:
----------------------------------
FYI, I'm releasing 0.7.0.Final, which includes SRAMP-626
> Eclipse IDE: S-RAMP tooling
> ---------------------------
>
> Key: SRAMP-16
> URL: https://issues.jboss.org/browse/SRAMP-16
> Project: S-RAMP
> Issue Type: Task
> Components: IDE Integration
> Affects Versions: 0.6.0.Final
> Reporter: Kurt Stam
> Assignee: Brett Meyer
> Attachments: UIMockup.gliffy, UImockup.gliffy
>
>
> Introducing IDE-based tooling, interacting with the S-RAMP repo, brings up several interesting use cases. For instance, allowing an app developer to search for a WSDL in S-RAMP, then pull it down into his/her project (all from within the IDE) would be powerful.
> One idea would be to look into writing this as a JBoss Forge plugin. Not only would we gain Eclipse support, but also any other Forge-supported environment. The unknown is how to integrate that plugin with an Eclipse view UI, as opposed to simply relying on the Forge shell.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years
[JBoss JIRA] (SRAMP-624) Handle expanded artifacts in updateContent/deleteContent
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-624?page=com.atlassian.jira.plugin.... ]
Brett Meyer closed SRAMP-624.
-----------------------------
Resolution: Won't Fix
For now, not fixing this. Since the expanded artifacts are themselves *primary*, imo it's different than automatically deleting derived artifacts. Clients can always query on the expandedFromDocument relationship and delete, if necessary.
> Handle expanded artifacts in updateContent/deleteContent
> --------------------------------------------------------
>
> Key: SRAMP-624
> URL: https://issues.jboss.org/browse/SRAMP-624
> Project: S-RAMP
> Issue Type: Enhancement
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> updateContent/deleteContent currently clears out the artifacts derived from the given artifact. What if an archive is updated/deleted? Should all of its expanded artifacts also be removed?
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years