Here's the output

mbcandide:~ candide$ curl --insecure -H "Authorization: Bearer 
daErBhdMqevWAT3NnATQXFgd1RcNMR81HZb2SWN2aOs" 
https://paas.intrinsic.world:8443/api/v1/proxy/namespaces/default/services/fabric8-forge/

Error: 'dial tcp 10.1.0.9:8080: i/o timeout'
Trying to reach: 'http://10.1.0.9:8080/'

Sorry, but I just don't understand how to use your answer: as a user, I don't 
have control over what kind of token is passed. I can only guess that something 
got somehow misconfigured at the cluster level and I'm looking for advice on 
how to fix the bigger picture of why things aren't "just working" as they 
should...


> On 19 Jan 2016, at 20:40, David Eads <[email protected]> wrote:
> 
> Could you include the output of that curl?  If you provide an expired or 
> invalid token, you'll get a "401 unauthorized", not a 403 forbidden that 
> indicates "system:anonymous" cannot "proxy".  In order to get the 403, you 
> (or the product calling on your behalf), must be making the request without 
> any token at all.
> 
> You should use a token for a user that has sufficient power to proxy to that 
> service.
> 
> On Tue, Jan 19, 2016 at 2:17 PM, Candide Kemmler <[email protected] 
> <mailto:[email protected]>> wrote:
> This is a follow-up to thread I started on the fabric8 mailing-list. It's 
> bouncing to this list because it looks like the issue is related to 
> OpenShift, not fabric8.
> 
> The entire thread is here: 
> https://groups.google.com/forum/#!topic/fabric8/OgDXCAoGO1I 
> <https://groups.google.com/forum/#!topic/fabric8/OgDXCAoGO1I>
> 
> To reproduce the bug, login to http://fabric8.apps.intrinsic.world 
> <http://fabric8.apps.intrinsic.world/> using admin/admin, go to develop -> 
> default -> Create Project -> Create Java Project using Wizard and look what's 
> going on in the console.
> 
> The fabric8 folks say they can reproduce the issue by simply calling
> 
> curl --insecure -H "Authorization: Bearer 
> daErBhdMqevWAT3NnATQXFgd1RcNMR81HZb2SWN2aOs" 
> https://paas.intrinsic.world:8443/api/v1/proxy/namespaces/default/services/fabric8-forge/
>  
> <https://paas.intrinsic.world:8443/api/v1/proxy/namespaces/default/services/fabric8-forge/>
> 
> ...although I don't fully understand what this means
> 
> My installation notes for the OpenShift setup are here: 
> https://www.evernote.com/l/ACjvdVhtZ_pAZaJAtgVQJPn51-hS8huMVaI 
> <https://www.evernote.com/l/ACjvdVhtZ_pAZaJAtgVQJPn51-hS8huMVaI>
> 
> Any help will be highly appreciated: our goal is to be able to use Fabric8 on 
> a real cloud and start experimenting with it. If the ansible method to 
> installling OS isn't working, any workaround will do. So far though Ansible 
> has been the single most reliable way to get something going on the cloud. 
> Also, wondering how it will be possible to benefit from patches and updates...
> 
> Candide
> 
> _______________________________________________
> users mailing list
> [email protected] <mailto:[email protected]>
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users 
> <http://lists.openshift.redhat.com/openshiftmm/listinfo/users>
> 

_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Reply via email to