Almost any website you visit today is protected by HTTPS. If yours isn’t yet, it should be. Securing your server with HTTPS also means that you can’t send requests to this server from one that isn’t protected by HTTPS. This poses a problem for developers who use a local development environment because all of them run on http://localhost out-of-the-box.

What Does Node Wants To Use The Local Items Keychain Mean
Node Wants To Use The Local Items Keychain Using
Node Wants To Use The Local Items Keychain To Be

One of these apparently minor irritations, but something that is also a symptom of a bigger problem is the message “accountsd wants to use the login keychain” appearing repeatedly on-screen. In this article, we’ll tell you what accountsd is, why it keeps asking for access to the login keychain, and what you should do about it. Node wants to use the “Local Items” Keychain Usually it’s sharingitems, which negotiates AirDrop, Handoff, Instant Hotspot, Shared Computers, and Remote Disc. Or it could be the Login keychain - you might find the link below to be useful. SOLVED: Mac Keeps Asking for Keychain “Local Items” Password. If the issue is with your Computer or a Laptop you should try using Restoro which can scan the repositories and replace corrupt and missing files. This works in most cases, where the issue is originated due to a system corruption.

At the startup I’m a part of, we decided to secure our AWS Elastic Load Balancer endpoints with HTTPS as part of a move to enhance security. I ran into a situation where my local development environment’s requests to the server started getting rejected.

A quick Google search later, I found several articles like this, this or this one with detailed instructions on how I could implement HTTPS on localhost. None of these instructions seemed to work even after I followed them religiously. Chrome always threw a NET::ERR_CERT_COMMON_NAME_INVALID error at me.

The problem

All the detailed instructions I had found were correct for the time they were written. Not anymore.

After a ton of Googling, I discovered that the reason for my local certificate getting rejected was that Chrome had deprecated support for commonName matching in certificates, in effect, requiring a subjectAltName since January 2017.

The solution

We’ll be using OpenSSL to generate all of our certificates.

Step 1: Root SSL certificate

The first step is to create a Root Secure Sockets Layer (SSL) certificate. This root certificate can then be used to sign any number of certificates you might generate for individual domains. If you aren’t familiar with the SSL ecosystem, this article from DNSimple does a good job of introducing Root SSL certificates.

Generate a RSA-2048 key and save it to a file rootCA.key. This file will be used as the key to generate the Root SSL certificate. You will be prompted for a pass phrase which you’ll need to enter each time you use this particular key to generate a certificate.

What Does Node Wants To Use The Local Items Keychain Mean

You can use the key you generated to create a new Root SSL certificate. Save it to a file namedrootCA.pem. This certificate will have a validity of 1,024 days. Feel free to change it to any number of days you want. You’ll also be prompted for other optional information.

Step 2: Trust the root SSL certificate

Before you can use the newly created Root SSL certificate to start issuing domain certificates, there’s one more step. You need to to tell your Mac to trust your root certificate so all individual certificates issued by it are also trusted.

Open Keychain Access on your Mac and go to the Certificates category in your System keychain. Once there, import the rootCA.pem using File > Import Items. Double click the imported certificate and change the “When using this certificate:” dropdown to Always Trust in the Trust section.

Your certificate should look something like this inside Keychain Access if you’ve correctly followed the instructions till now. = james stamp trumpet method warm-up book.

Step 2: Domain SSL certificate

The root SSL certificate can now be used to issue a certificate specifically for your local development environment located at localhost.

Create a new OpenSSL configuration file server.csr.cnf so you can import these settings when creating a certificate instead of entering them on the command line.

Create a v3.ext file in order to create a X509 v3 certificate. Notice how we’re specifying subjectAltName here.

Create a certificate key for localhost using the configuration settings stored in server.csr.cnf. This key is stored in server.key.

A certificate signing request is issued via the root SSL certificate we created earlier to create a domain certificate for localhost. The output is a certificate file called server.crt.

Use your new SSL certificate

You’re now ready to secure your localhost with HTTPS. Move the server.key and server.crt files to an accessible location on your server and include them when starting your server.

In an Express app written in Node.js, here’s how you would do it. Make sure you do this only for your local environment. Do not use this in production.

I hope you found this tutorial useful. If you’re not comfortable with running the commands given here by yourself, I’ve created a set of handy scripts you can run quickly to generate the certificates for you. More details can be found on the GitHub repo.

I love helping fellow web developers. Follow me on Twitter and let me know if you have any suggestions or feedback. If you’d like to show your appreciation towards any of the work I’ve done, be it a blog post, an open source project or just a funny tweet, you can buy me a cup of coffee.

When an Adobe app launches, it displays Adobe Licensing dialog box while accessing Keychain on macOS

When an app launches, sometimes one of the following dialog boxes display.

adobe_license_helper prompts for Keychain access to the Login keychain

The adobe_licencing_helper is used to check the entitlements of the software when an application launches. Since runtime information is stored in the login keychain, the licensing dialog displays if the Adobe app does not have access to the keychain. Access to the keychain can be blocked due to several reasons such as:

The keychain is locked
Access control of Adobe-specific keys in the keychain is set to Confirm before allowing access

To allow access to the keychain, enter your password and then click OK or Always Allow.

Your keychain password is usually the same as your macOS login password, unless you've used the Keychain Access app to change it.

To prevent the keychain prompts, you can ensure the following:

Keychain is unlocked when Adobe applications are launched.
Keychain does not get locked automatically after a specified period of time or when your device is sleeping.
Default keychain entries access permissions are not manually modified. That is, access control of Adobe-specific keys (inside login/Secure Notes) in the keychain is set to Allow all applications to access this item.

Node Wants To Use The Local Items Keychain Using

If setting the Adobe specific keys in the Keychain to Allow all applications to access this item does not resolve the issue, try the following:

Node Wants To Use The Local Items Keychain To Be

Change Setting for the login keychain and extend the time after which the keychain locks automatically.
Lock and then unlock your login keycha