can't get Consumer ID after uploading RSA keys - walmart-api

This is my first time trying to access the Walmart API. I created my account and followed the onboarding steps but I can't get the Dashboard to generate "consumer ID" for me.
I have created my application, and click on “Upload/Update public key”. I copy-pasted two RSA public keys into the field; one for Staging, and one for Production. However it never creates the “Consumer ID” for my application. Can you see my dashboard entry in your system?
Why am I not issued a consumer ID after uploading my public keys?

Usually the issue will be either
the public key is invalid (or)
if you already have consumer id and trying to update with the same public key then there will be an issue (or)
if you have copied public key along with any white spaces (or)
if you are trying to upload private key by mistake
Regards,
Firdos
IO Support

Related

How is a public key used that is generated when a Microsoft Edge extension is submitted on Partner Center?

While uploading my extension to Microsoft Partner Centre, I have got a "Public key" for my extension along with CRX ID and Store ID.
I could not find any documentation on the use of this Public key in Microsoft Edge Add-ons. Can I know the use of this key?
The only thing I can find about public key in Microsoft doc is this:
The extension ID is generated based on a hash of the public key.
So I think the use of the public key is to generate extension ID.

What exactly is my Common Name for a certificate-signing request

I'm trying to generate a certificate-signing request file, in order to generate a .p12 certificate for Azure Notification Hub so I can send push notifications. I'm following this guide:
https://learn.microsoft.com/en-us/azure/notification-hubs/xamarin-notification-hubs-ios-push-notification-apns-get-started#generate-the-certificate-signing-request-file
I'm just a little confused about the information I'm supposed to provide for the CSR.
User Email Address = I assume is the email associated with the account I'm current logged into the Mac with.
Common Name = This what I am confused by. The guide I referenced above simply says "Enter your Common Name". When I google about finding what my common name is, I see information about domain names and servers suggesting that the common name should be example.com. But I'm just trying to test push notifications with my Mac, I don't have a domain name...
Here is some of my search references:
https://www.ssl.com/how-to/csr-generation-in-macos-keychain-access/
https://support.dnsimple.com/articles/what-is-common-name/
What am I missing here?
Regarding APNS I'm using always the name of the private key in the keychain as common name.

Can't import Code-signing Public or Private keys using Keychain access (Mac OS X Mavericks)

In an attempt to build an iOS project (in XCode), I need to import my colleague's public and private keys for the code signing identity, but I am unable to do so because I get an error in Keychain Access that says "An error has occurred. Unable to import an item. / The contents of this item cannot be retrieved"
FULL DETAILS:
I have got two keys from my colleague's computer, exported them from his Keychain as two files:
Roomer Inc.p12 (the private key)
Roomer Inc.pem (the public key)
When he exported these, he left the password blank (Although we also tried with a password of "test" and got the same results).
When I double-click Roomer Inc.p12 (for the private key), it opens in Keychain Access and promts me to choose the keychain ("login" is selected by default)
I click "Add" and then I am prompted for the password to the keychain (which I leave blank)
Next I always see this message in Keychain access:
However, despite this message appearing, when I click OK, I see a new private key entry for "Roomer Inc". Note that this entry is a private key in the "login" key chain as I would expect, but has no expiration date (should it?)
Next, for the Roomer Inc.pem file (the public key) I am asked to choose the keychain ("login") and I click Add
Then, I also get the "An error has occurred. Unable to import an item. / The contents of this item cannot be retrieved" message for the public key as well. In this case however (unlike the Private key), I do not see any entry corresponding for what I just added.
So, it appears that the private key entry may or may not be OK (I have no way to verify), and the public key entry for Roomer cannot be installed in the keychain without this error message. Please note that I also tried using the security import command to import the public key :
$ security import Roomer\ Inc.pem -f pkcs12 ~/Library/Keychains/login.keychain
1 key imported.
When I do this, although the command returns "1 key imported" I do not see a public key for "Roomer Inc" in my Keychain Access window (I closed out Keychain Access and re-opened it).
Either way, we have identified that this is our blocker. (The symptom of course is that the XCode project won't build for the AdHoc provisioning profile to be used with TestFlight). I have left off the additional steps regarding the XCode build and TestFlight setup, because we believe the core problem has to do with importing the keys as explained above.
We figured out our problem, and I am posting my answer here so that others may find it helpful.
The problem is really a UX problem with Keychain Access. Let me back up and give a little context: when you create a distribution certificate with Apple, you create it based on a PRIVATE KEY and App-based permissions.
In Keychain Access, the distribution certificate is listed as a child below the name of the private key that it was created from. Here's the catch: When you use the search box in Keychain access (in my case we were typing in "Roomer" because that's the name on our distribution certificate), it won't look for a certificate with that name, it will look for a certificate attached to a private key for that name.
So my colleague had create a distribution certificate based on a private key that was named "Jorge Davila" (his name), even though the distribution certificate was named "iPhone Distribution: Roomer Inc."
When he searched for "Roomer" in Keychain Access, the correct one was NOT displayed in the search results because the key this certificate was created from was named "Jorge Davila" not "Roomer". Thus, he was exporting the wrong certificate and didn't realize because there were others (some expired) with that name.
Here's how the correct one looks:
This is a relatively nuanced problem with the UX of Keychain Access and the fact that the search tool doesn't give you the results you expect it to. I am posting this answer in the hope that others may find it useful.

Accuring reference to public key status in braintree IOS

I'm developing an iOS Project using a Braintree Payment roll for transaction processing. I'm using the API at SCViewController.m line 86 from the Braintree iOS Library and that code was working perfectly.
I created a new Braintree Sandbox accout and put its encryption key into our project, but now I get this error:
Problem acquiring reference to the public key, OSStatus == 0
What do I need to do to make the new encryption key work in my project?
The SampleProject is creating a VTClient object here. When that object is created, you pass in your Braintree client-side encryption key and your merchant ID.
That error is happening because you're passing in an incorrect Braintree client-side encryption key. Please make sure that you're using the correct sandbox client-side encryption key and sandbox merchant ID, which can be found logging in to the sandbox Braintree site.
Also, keep in mind that there are different client-side encryption keys and merchant IDs for sandbox vs production environments. When you create the VTClient, you can specify which environment you're working in - and ensure that you're passing in the appropriate credentials for that environment.
Braintree dev here - as a result of some recent internal upgrades, a small number of CSE keys in our sandbox were generated incorrectly. From your error message, it looks like you may have been bit by this issue.
We've regenerated keys for the affected users. If you go back to the Sandbox and copy your new CSE key, it should now work. If it doesn't, please reach out to our support (support#braintreepayments.com) directly and we'll be in touch.
Thanks,
-SP

Not able to install signature keys

I have to sign a BlackBerry application so that I can load it onto the device, but the system that the signature keys I got from RIM are installed on got formatted. Now I am trying to install the signature keys on another system, but the server prompts me for this:
"Unable to register client '2909103544' because there are no more registration attempts. If you have already registered with this server, then you must contact RIM to register additional user."
Can we install these keys on only one single computer? Do I now have to purchase new keys?
you have to re purchase the keys, since they are for single developer, single pc
BlackBerry JDE Plug-in for Eclipse Users:
Save all 3 .csi files in the same directory (each one will be sent in a separate email message).
Start Eclipse.
Click on the BlackBerry menu and choose Install Signature Keys.
Select one of the 3 .csi files saved in step 1 and click Open.
Click "Yes" to create a new key pair file.
Type a password for your private key of at least 8 characters, and type it again to confirm. This is your private key password, which protects your private key. Please remember this password as you will be prompted for it each time signing is attempted or a signature key is installed.
Move your mouse to generate date for a new private key.
In the Registration PIN" field, type the PIN number that you supplied on the signature key order form.
In the Private Key password field, type the password created in step 6.
Click Register .
Click Exit .
Repeat this process for the other csi files.

Resources