July 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (ARTIF-739) Upgrade Keycloak to 1.3.x

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-739?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-739: ------------------------------ Fix Version/s: 1.1.0.Final (was: 1.0.0.Final) > Upgrade Keycloak to 1.3.x > ------------------------- > > Key: ARTIF-739 > URL: https://issues.jboss.org/browse/ARTIF-739 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-730) Support Wildfly 9

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-730?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-730: ------------------------------ Fix Version/s: 1.1.0.Final (was: 1.0.0.Final) > Support Wildfly 9 > ----------------- > > Key: ARTIF-730 > URL: https://issues.jboss.org/browse/ARTIF-730 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-746) CLI: GetContentCommand's output file should be optional

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-746?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved ARTIF-746. ------------------------------- Resolution: Done > CLI: GetContentCommand's output file should be optional > ------------------------------------------------------- > > Key: ARTIF-746 > URL: https://issues.jboss.org/browse/ARTIF-746 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Final > > > Default to printing to the console -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-745) CLI: GetContentCommand won't overwrite an existing file

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-745?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved ARTIF-745. ------------------------------- Resolution: Done > CLI: GetContentCommand won't overwrite an existing file > ------------------------------------------------------- > > Key: ARTIF-745 > URL: https://issues.jboss.org/browse/ARTIF-745 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-744) CLI: GetContentCommand's --help doesn't work

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-744?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved ARTIF-744. ------------------------------- Resolution: Done > CLI: GetContentCommand's --help doesn't work > -------------------------------------------- > > Key: ARTIF-744 > URL: https://issues.jboss.org/browse/ARTIF-744 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Final > > > May need to debug Aesh or its logs to figure out why -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-744) CLI: GetContentCommand's --help doesn't work

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-744?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-744: ----------------------------------- Only affected commands with required options. --help simply needed 'overrideRequired = true' on its @Option. > CLI: GetContentCommand's --help doesn't work > -------------------------------------------- > > Key: ARTIF-744 > URL: https://issues.jboss.org/browse/ARTIF-744 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Final > > > May need to debug Aesh or its logs to figure out why -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-746) CLI: GetContentCommand's output file should be optional

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-746?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-746: ------------------------------ Fix Version/s: 1.0.0.Beta3 > CLI: GetContentCommand's output file should be optional > ------------------------------------------------------- > > Key: ARTIF-746 > URL: https://issues.jboss.org/browse/ARTIF-746 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Final > > > Default to printing to the console -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-745) CLI: GetContentCommand won't overwrite an existing file

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-745?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-745: ------------------------------ Fix Version/s: 1.0.0.Beta3 > CLI: GetContentCommand won't overwrite an existing file > ------------------------------------------------------- > > Key: ARTIF-745 > URL: https://issues.jboss.org/browse/ARTIF-745 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-748) Web UI: Refresh to /login when Keycloak token expires

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-748?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-748: ------------------------------ Description: If the token expires, the server spits out: 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} The next time the browser makes a call to the UI services, Errai reports an uncaught GWT exception. That call *must* be protected by Keycloak, in order for our Filter to pick up the KeycloakSecurityContext and create the bearer token. However, the GWT exception shows that the Keycloak *login page* is being served on the call, so Errai's JSON marshaller barfs on the HTML. APIMan (Angular UI) checks for a 401 response code and automatically refreshes the browser to combat this. However, I'm not sure if that's possible in this case. Our use of Errai's "Caller" pattern isn't kicking in for these errors (completely sidesteps the ErrorHandler), I'm guessing due to it being a lower level issue with the GWT marshaller. Idea: Have a pure Javascript loop "ping" the UI services and check the response. was: If the token expires, the server spits out: 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} The next time the browser makes a call to the UI services, Errai reports an uncaught GWT exception. That call *must* be protected by Keycloak, in order for our Filter to pick up the KeycloakSecurityContext and create the bearer token. However, the GWT exception shows that the Keycloak *login page* is being served on the call, so Errai's JSON marshaller barfs on the HTML. APIMan checks for a 401 response code and automatically refreshes the browser to combat this. However, I'm not sure if that's possible in this case. Our use of Errai's "Caller" pattern isn't kicking in for these errors (completely sidesteps the ErrorHandler), I'm guessing due to it being a lower level issue with the GWT marshaller. Idea: Have a pure Javascript loop "ping" the UI services and check the response. > Web UI: Refresh to /login when Keycloak token expires > ----------------------------------------------------- > > Key: ARTIF-748 > URL: https://issues.jboss.org/browse/ARTIF-748 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > > If the token expires, the server spits out: > 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token > 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} > The next time the browser makes a call to the UI services, Errai reports an uncaught GWT exception. That call *must* be protected by Keycloak, in order for our Filter to pick up the KeycloakSecurityContext and create the bearer token. However, the GWT exception shows that the Keycloak *login page* is being served on the call, so Errai's JSON marshaller barfs on the HTML. > APIMan (Angular UI) checks for a 401 response code and automatically refreshes the browser to combat this. However, I'm not sure if that's possible in this case. Our use of Errai's "Caller" pattern isn't kicking in for these errors (completely sidesteps the ErrorHandler), I'm guessing due to it being a lower level issue with the GWT marshaller. > Idea: Have a pure Javascript loop "ping" the UI services and check the response. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-748) Web UI: Refresh to /login when Keycloak token expires

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-748?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-748: ----------------------------------- [~eric.wittmann], thanks again for the help. Am I missing anything here? > Web UI: Refresh to /login when Keycloak token expires > ----------------------------------------------------- > > Key: ARTIF-748 > URL: https://issues.jboss.org/browse/ARTIF-748 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > > If the token expires, the server spits out: > 14:25:07,534 WARN [org.keycloak.events] (default task-36) type=REFRESH_TOKEN_ERROR, realmId=0c4049da-2746-468e-ab6d-49e51dd1f133, clientId=artificer-ui, userId=null, ipAddress=127.0.0.1, error=invalid_token > 14:25:07,560 ERROR [org.keycloak.adapters.RefreshableKeycloakSecurityContext] (default task-37) Refresh token failure status: 400 {"error_description":"Refresh token expired","error":"invalid_grant"} > The next time the browser makes a call to the UI services, Errai reports an uncaught GWT exception. That call *must* be protected by Keycloak, in order for our Filter to pick up the KeycloakSecurityContext and create the bearer token. However, the GWT exception shows that the Keycloak *login page* is being served on the call, so Errai's JSON marshaller barfs on the HTML. > APIMan checks for a 401 response code and automatically refreshes the browser to combat this. However, I'm not sure if that's possible in this case. Our use of Errai's "Caller" pattern isn't kicking in for these errors (completely sidesteps the ErrorHandler), I'm guessing due to it being a lower level issue with the GWT marshaller. > Idea: Have a pure Javascript loop "ping" the UI services and check the response. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues July 2015