# DOI registration

**URL:** <https://community.crossref.org/t/doi-registration/13545>\
**Category:** OJS Users\
**Tags:** ojs, content-registration, journal\
**Created:** [4 April 2025 13:23 UTC](https://community.crossref.org/t/doi-registration/13545 "2025-04-04T13:23:31Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![giuliarlopes](https://avatars.discourse-cdn.com/v4/letter/g/e19b73/32.png) [@giuliarlopes](https://community.crossref.org/u/giuliarlopes)\
**Post date:** [4 April 2025 13:23 UTC](https://community.crossref.org/t/doi-registration/13545/1 "2025-04-04T13:23:31Z")

</div>

I’ve tried to register content for one of our journals via the OJS Crossref export plugin, but have run into a 401 error.

_Registration was not successful! The DOI registration server returned an error: ’(401 Unauthorized)'._

I’ve tried submitting the XML on the crossref administration platform, but I’ve run into another error message about “not being authorized to submit”.

I’ve tested re-depositing another journal’s DOI and it does not seem to be a member issue, but only an issue with this one prefix/user. This user has been depositing DOIs for years without a problem until now.

I saw another person having the same trouble in our forum, the crossref team was able to help them. How should I proceed?

Thank you, Giulia

---

<div class="post-metadata">

**Author:** ![Shayn](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/shayn/32/57_2.png) [@Shayn](https://community.crossref.org/u/Shayn)\
**Post date:** [4 April 2025 13:56 UTC](https://community.crossref.org/t/doi-registration/13545/2 "2025-04-04T13:56:29Z")

</div>

Hi Giulia.

Thanks for your message.

Could you tell me the DOI prefix for this journal?

Thanks,  
Shayn

---

<div class="post-metadata">

**Author:** ![giuliarlopes](https://avatars.discourse-cdn.com/v4/letter/g/e19b73/32.png) [@giuliarlopes](https://community.crossref.org/u/giuliarlopes)\
**Post date:** [4 April 2025 14:05 UTC](https://community.crossref.org/t/doi-registration/13545/3 "2025-04-04T14:05:31Z")

</div>

Hi, Shayn.

The prefix is 10.23901

Thank you for your time!

Best regards,  
Giulia

---

<div class="post-metadata">

**Author:** ![Shayn](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/shayn/32/57_2.png) [@Shayn](https://community.crossref.org/u/Shayn)\
**Post date:** [4 April 2025 14:17 UTC](https://community.crossref.org/t/doi-registration/13545/4 "2025-04-04T14:17:34Z")

</div>

Thanks for that information.

That member account, Revista Ciencia em Extensao – RCE, currently does not have permissions to register new DOIs.

You’ll need to contact their sponsoring organization, ABEC Brasil, for more information about that.

---

<div class="post-metadata">

**Author:** ![giuliarlopes](https://avatars.discourse-cdn.com/v4/letter/g/e19b73/32.png) [@giuliarlopes](https://community.crossref.org/u/giuliarlopes)\
**Post date:** [4 April 2025 15:10 UTC](https://community.crossref.org/t/doi-registration/13545/5 "2025-04-04T15:10:32Z")

</div>

Thank you, Shayn.

Could you please check if that prefix does also not have a permission?  
Prefix: 10.32929

Thanks,  
Giulia

---

<div class="post-metadata">

**Author:** ![Shayn](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/shayn/32/57_2.png) [@Shayn](https://community.crossref.org/u/Shayn)\
**Post date:** [4 April 2025 15:36 UTC](https://community.crossref.org/t/doi-registration/13545/6 "2025-04-04T15:36:28Z")

</div>

Yes, the same is true for Revista Cultura Agronomica (prefix 10.32929)

---

<div class="post-metadata">

**Author:** ![fusionproceedings](https://avatars.discourse-cdn.com/v4/letter/f/439d5e/32.png) [@fusionproceedings](https://community.crossref.org/u/fusionproceedings)\
**Post date:** [3 June 2025 05:18 UTC](https://community.crossref.org/t/doi-registration/13545/7 "2025-06-03T05:18:35Z")

</div>

Dear Crossref Support Team,

Thank you for confirming our Crossref membership and assigning us the DOI prefix 10.63995. I have a journal operating on the OJS platform, and I have registered the membership credentials in the Crossref plugin accordingly.

However, I am encountering an error when attempting to register DOIs for articles. The system returns the following message:

Registration Error Message:  
(401 Unauthorized)  
“There has been a problem locating a publisher for this DOI. Our system shows no member with the prefix 10.63995.”

I have also attached a screenshot of the error for your reference.

Could you please help us resolve this issue? It appears there may be a mismatch or delay in activating the DOI prefix or linking it to our membership account.

We would appreciate your guidance on how to proceed.

Thank you for your support.

---

<div class="post-metadata">

**Author:** ![collinks](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/collinks/32/2153_2.png) [@collinks](https://community.crossref.org/u/collinks)\
**Post date:** [3 June 2025 16:11 UTC](https://community.crossref.org/t/doi-registration/13545/8 "2025-06-03T16:11:49Z")

</div>

Hi @fusionproceedings team,

Thanks for the question. A 401 error in OJS usually means that there’s a problem with the credentials you’re using to deposit metadata with us. These credentials are set up through the screen in OJS shown in Step 3 at [this page](https://www.crossref.org/documentation/register-maintain-records/ojs-plugin/).

 ![A screenshot of the OJS plugin's setup page. There are four fields; Depositor name, Depositor email, Username, and Password. The Username is in the form of "email address/role".](https://us1.discourse-cdn.com/flex020/uploads/crossref/original/2X/4/433f442ea5a09e41fc5474274366367a590382c8.png)  
The 401 error usually comes about as a result of folks just entering their email address, rather than their email address **and role** to the Username field. Can you confirm that your username is in the form of `email@domain.tld/role` and that your Password is the same password you set up when I completed your account setup last week?

Once all of this is updated, please retry a deposit and let us know if you’re still encountering this 401 error.
