curl - Jive REST API returning {"code":401,"message":"Bad credentials"} using Basic Auth -
this may not specific jive api, basic auth in general.
this not federated account.
i'm attempting simple request jive rest api v3 curl:
curl --include --verbose --user {username}:{password} 'https://sandbox.jiveon.com/api/core/v3/search/contents?filter=search(test)' i tried:
curl -v -u username "https://sandbox.jiveon.com/api/core/v3/contents?count=100&startindex=200" i can login ui credentials (and regardless, have "full access" rights anyway). why 401 being thrown? authentication malformed?
here's example i'm following:
https://developer.jivesoftware.com/rest
and here's relevant results:
trying 23.221.10.251... connected sandbox.jiveon.com (23.221.10.251) port 443 (#0) tlsv1.0, tls handshake, client hello (1): tlsv1.0, tls handshake, server hello (2): tlsv1.0, tls handshake, cert (11): tlsv1.0, tls handshake, server finished (14): tlsv1.0, tls handshake, client key exchange (16): tlsv1.0, tls change cipher, client hello (1): tlsv1.0, tls handshake, finished (20): tlsv1.0, tls change cipher, client hello (1): tlsv1.0, tls handshake, finished (20): ssl connection using tlsv1.0 / aes128-sha server certificate: subject: ou=domain control validated; ou=comodo ssl wildcard; cn=*.jiveon.com start date: 2014-06-23 00:00:00 gmt expire date: 2015-07-31 23:59:59 gmt subjectaltname: sandbox.jiveon.com matched issuer: c=gb; st=greater manchester; l=salford; o=comodo ca limited; cn=comodo ssl ca 2 ssl certificate verify ok. server auth using basic user 'username omitted here' /api/core/v3/contents?count=100&startindex=200 http/1.1 authorization: basic xxxxxxxxxxxxxxxxxx= (i verified decoded in base64) user-agent: curl/7.41.0 host: sandbox.jiveon.com accept: */* http/1.1 401 unauthorized
for stumbles across this, user/password credentials fine - sending request wrong instance https://sandbox.jiveon.com. client who's migrating jive, , provided user accounts on uat instance, appears cannot receive responses sandbox instance type of account.
sending request https://{our jive org url}/api/core/v3 worked fine.
Comments
Post a Comment