Answering to myself:
https://github.com/openshift/origin/issues/13161
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Thanks! That's what I was looking for.
On Wed, 14 Jun 2017 at 01:37 Clayton Coleman wrote:
> /oauth/info should return info about the token you pass as Authorization:
> Bearer
>
> On Mon, Jun 12, 2017 at 9:38 PM, Andrew Lau wrote:
>
>> Is there an endpoint to retrieve the current token informat
/oauth/info should return info about the token you pass as Authorization:
Bearer
On Mon, Jun 12, 2017 at 9:38 PM, Andrew Lau wrote:
> Is there an endpoint to retrieve the current token information?
>
> ie. /oapi/v1/users/~ seems to be an undocumented way to get the current
> user information. I'
Title: Re: oauth token info
Hi Andrew Lau.
on Dienstag, 13. Juni 2017 at 12:14 was written:
Normal users can't query those endpoints
That's true.
I think then the easiest way is to use
https://jwt.io/ or
https://github.com/auth0/jwt-decode
Regards
Aleks
On Tue, 13 Jun 2017 at 17:
ps: the image is an imageStream in the same namespace.
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Hey Julio,
Setting openshift_ip as a host level variable within inventory will
override the IP that is selected by default for etcd hosts (IP of the
default route).
playbooks/byo/openshift-cluster/redeploy-etcd-certificates.yml can be used
to replace the etcd certificates with the overridden IP va
more clues
etcd nodes have two ips, public an private
for some reason open shift is creating the certificates using de public ip
instead of private
so connecting to etcd gives me and error saying certificate is generated to
this IP and not to that IP
so it fails for that reason after re gener
Hi,
I created a cronJob (
https://docs.openshift.com/container-platform/3.5/dev_guide/cron_jobs.html)
in a project on openshift 1.5, and the job fails to start with:
Failed to pull image "...": unauthorized: authentication required
Error syncing pod, skipping: failed to "StartContainer" for "...
more info
i managed to connect with curl to the etcd server and queried about controller
keys
{"action":"get","node":{"key":"/openshift.io/leases/controllers","value":"master-lyy7bxfg","expiration":"2017-05-31T10:26:28.833756573Z","ttl":-1128220,"modifiedIndex":20547532,"createdIndex":18120566}
sorry about wget
connecting to etcd nodes using openssl and passing client certs looks good
openssl s_client -cert master.etcd-client.crt -key master.etcd-client.key
-connect etcd-node1:2379 -debug
connects without problem
but api service does not
Jun 13 15:25:04 openshift-master01 origin-m
Hello
i have a problem in a 1.2.0 cluster with etcd ca and certificates, mainly they
did expire
i followed the doc regarding this and after update my openshift-ansible i got
the needed playbook
after running em i see etcd certs and ca are updated on my nodes, and dumping
them with openssl loo
Normal users can't query those endpoints
On Tue, 13 Jun 2017 at 17:46 Aleksandar Lazic wrote:
> Hi Andrew Lau.
>
> on Dienstag, 13. Juni 2017 at 03:38 was written:
>
>
> Is there an endpoint to retrieve the current token information?
>
> ie. /oapi/v1/users/~ seems to be an undocumented way to ge
Title: Re: oauth token info
Hi Andrew Lau.
on Dienstag, 13. Juni 2017 at 03:38 was written:
Is there an endpoint to retrieve the current token information?
ie. /oapi/v1/users/~ seems to be an undocumented way to get the current user information. I'm looking to obtain the expiry time on the
13 matches
Mail list logo
