 |
 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey all, There's a gap in my Sierra API, or curl knowledge and I am hoping some of you who read this can fill up. III uses OAuth v2.O's "Client Credentials Grant" [0] to play. If I am reading that RFC correctly. I should get a token back if I use curl --user the_client:secret --data "grant_type=client_credentials" https://lib.example.edu/iii/sierra-api/v1/token In my case this results "invalid grant" error. Thanks for pointing me to "ideally" a non-RFC document to figure out where this breaks down. I'd share the Sierra API documentation... but you know? Paywall. ;-) Cheers, ./fxk [0] http://tools.ietf.org/html/rfc6749#section-4.4 - -- Be conservative in what you do, be liberal in what you accept from others. (RFC 793) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTekc0AAoJEOptrq/fXk6MltIH/2oJN9XovZl25vC6VJlBMwJ8 5vnXLgyYHg/FfbpbSlZSxx57xqtNizSkYXy51TDtH5aSu0TSJmDG7PAgITMieN4G zpuaHsQVwq8ORybBts0q2LBUQxbMI2VIT/+02/B7AgFq8ha5ZAxwJbMh4kJx9aZA pqMfzKvGZH1QRrlbYktaUDCUQTncwPvxD5F0Ur5pVZa3VgQn5VU17EMwPkmv0vqh qXDp5YZwnw800D83hakpbHtbDQZOZlngMy+1j5PyhIbXjpTUOLakhJAYzgCHvEI/ 9JhXIbyOj33ASD+/Cldy+iGHjxzLQq26JgFGiUzW2p6WY8K/7TiiRyGw4PNJZ/Y= =YUbX -----END PGP SIGNATURE-----