[
https://issues.apache.org/jira/browse/JCLOUDS-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul updated JCLOUDS-708:
--------------------------------
Description:
While testing the latest GCS pull request[1] I found that starting my
application then waiting 12 hours resulted in authentication errors:
{noformat}
org.jclouds.rest.AuthorizationException: {
"error": {
"errors": [
{
"domain": "global",
"reason": "authError",
"message": "Invalid Credentials",
"locationType": "header",
"location": "Authorization"
}
],
"code": 401,
"message": "Invalid Credentials"
}
}
{noformat}
Restarting my application worked around this issue although GCS should renew
its authorization token periodically as other providers do.
[1] https://github.com/jclouds/jclouds-labs-google/pull/48
was:
While testing the latest GCS pull request[1] I found that starting my
application then waiting 12 hours resulted in authentication errors:
{{noformat}}
org.jclouds.rest.AuthorizationException: {
"error": {
"errors": [
{
"domain": "global",
"reason": "authError",
"message": "Invalid Credentials",
"locationType": "header",
"location": "Authorization"
}
],
"code": 401,
"message": "Invalid Credentials"
}
}
{{noformat}}
Restarting my application worked around this issue although GCS should renew
its authorization token periodically as other providers do.
[1] https://github.com/jclouds/jclouds-labs-google/pull/48
> GCS does not renew authorization token after an interval
> --------------------------------------------------------
>
> Key: JCLOUDS-708
> URL: https://issues.apache.org/jira/browse/JCLOUDS-708
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-blobstore
> Affects Versions: 2.0.0
> Reporter: Andrew Gaul
> Assignee: Bhathiya Supun
>
> While testing the latest GCS pull request[1] I found that starting my
> application then waiting 12 hours resulted in authentication errors:
> {noformat}
> org.jclouds.rest.AuthorizationException: {
> "error": {
> "errors": [
> {
> "domain": "global",
> "reason": "authError",
> "message": "Invalid Credentials",
> "locationType": "header",
> "location": "Authorization"
> }
> ],
> "code": 401,
> "message": "Invalid Credentials"
> }
> }
> {noformat}
> Restarting my application worked around this issue although GCS should renew
> its authorization token periodically as other providers do.
> [1] https://github.com/jclouds/jclouds-labs-google/pull/48
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)