nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Child Item

-34018 Client has neither application-identfier nor keychain-access-groups entitlements

Tom N.16

When attempting to initiate oAuth with our in production app, I'm receiving this error below. Have not had an issue with this until today.

SecOSStatusWith error:[-34018] The operation couldn’t be completed. (OSStatus error -34018 - Remote error : The operation couldn‚Äôt be completed. (OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements))

Any help would be appreciated.

Find more posts tagged with

API

Abuse

Comments

Tom N.16

We're actually receiving a 401 when we request a token during oAuth v1. This is what we're sending in...

https://api.dropbox.com/1/oauth/request_token?oauth_consumer_key=MYKEY&oauth_nonce=D479682F-F1D8-4F19-BBD1-F9272ECFEFA7&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1441818375&oauth_version=1.0&oauth_signature=%2BPg51TkKV5Wb%2BNqTYF7VBvvY%3D

Tom N.16

Full error...

Error Domain=ASMHttpConnectionDomain Code=401 "Connection Error" UserInfo=0x3ba6ba0 {NSLocalizedRecoverySuggestion=unauthorized, Www-Authenticate=OAuth realm="https://api.dropbox.com/", Server=nginx, Transfer-Encoding=Identity, Connection=keep-alive, X-Dropbox-Request-Id=af86d3f0f923b0e2b184ca53918f429d, Content-Type=application/json, Date=Wed, 09 Sep 2015 17:24:45 GMT, NSLocalizedDescription=Connection Error}

Greg-DB

This 401 Unauthorized error should indicate that the oauth_signature is invalid, and I can't reproduce the error with a test implementation of OAuth 1 HMAC-SHA1 signing here.

HMAC-SHA1 signatures are intentionally opaque though and difficult to debug though. That being the case, we recommend using PLAINTEXT signing instead:

https://www.dropbox.com/developers/blog/20/using-oauth-in-plaintext-mode

Switching to PLAINTEXT would likely be the easiest solution. If you need to debug the HMAC-SHA1 signing though, please share the relevant code so we can take a look.

Tom N.16

I'm not sure what changed. We have several desktop apps that we publish on Mac and Windows and they all started failing oauth today. Can't go Plaintext plus we would have to go back and update a lot of different products and versions. I'll see about getting some code but I would think it would be something on the API oauth side that changed since this has been working for years and is failing on old versions as well as new of our apps.

Tom N.16

Not sure if this is going to help at all given nothing changed on our end but this is what we use on Mac. Our windows apps are failing oauth as well though.

BTW - thanks so much for your help.

We use the openssl library on mac

static CPString GenerateSignature(CPString Key, CPString Value)
{
    CPData keyData = Key;
    CPData valueData = Value;
    HMAC_CTX hmacContext;
    HMAC_CTX_init(&hmacContext);
    HMAC_Init_ex(&hmacContext, keyData.Bytes(), keyData.Length(), EVP_sha1(), NULL);
    HMAC_Update(&hmacContext, reinterpret_cast<const unsigned char*>(valueData.Bytes()), valueData.Length());
    unsigned char hashResult[EVP_MAX_MD_SIZE];
    unsigned int hashResultLength;
    HMAC_Final(&hmacContext, hashResult, &hashResultLength);
    return CPBase64Encoder::EncodeData(CPData::DataWithBytesOfLength(hashResult, hashResultLength));
}

Greg-DB

Thanks Tom. Are you able to copy over a sample request, including parameters, that produces by any chance? (You can open an API ticket if you prefer to share privately: https://www.dropbox.com/developers/contact )

Greg-DB

(That is, like the one in your second post, but including your key so we can try to compare.)

Tom N.16

Thanks Gregory. I'll post up via a API ticket given the key in the sample request.