# Depositing DOI registration xml using https POST

**URL:** <https://community.crossref.org/t/depositing-doi-registration-xml-using-https-post/2181>\
**Category:** Technical Support\
**Tags:** content-registration, https\_post\
**Created:** [23 October 2021 13:56 UTC](https://community.crossref.org/t/depositing-doi-registration-xml-using-https-post/2181 "2021-10-23T13:56:46Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![hbarkmann](https://avatars.discourse-cdn.com/v4/letter/h/3ec8ea/32.png) [@hbarkmann](https://community.crossref.org/u/hbarkmann)\
**Post date:** [23 October 2021 13:56 UTC](https://community.crossref.org/t/depositing-doi-registration-xml-using-https-post/2181/1 "2021-10-23T13:56:46Z")

</div>

Hi support,

I am a service provider to publishers in Germany, supporting them in metadata creation and distribution.

Currently I am trying to post files using the https POST method for user “woch” in publisher  
group " Wochenschau Verlag Dr. Kurt Debus GmbH".  
I am posting to [https://doi.crossref.org/servlet/deposit](https://doi.crossref.org/servlet/deposit) for user “woch” (login\_id) with its PW (login\_password)  
The credentials work well when signing in to the admin pages.  
The POST does not create an error but the file is never added to the submissions and I receive the following html as a response (removed some empty lines):

```auto
<!-- 

<br>
<font size=+1>

Welcome to Crossref.

</font>
<br><br>

<div id="browser-warning"></div>
<!--[if lt IE 9]>
    <style type="text/css">
        #browser-warning {
            display: none;
            background-color: #fde394;
            padding: 20px;
            max-width: 950px;
        }
        #browser-warning td.image {
        }
        #browser-warning img {
            max-height: 50px;
        }
        #browser-warning td.text {
            padding-left: 20px;
            padding-right: 20px;
            color: #4f5858;
            font-family: 'Open Sans', sans-serif;
            font-weight: bold;
        }
        #browser-warning .button {
            background-color: #3eb1c8;
            padding: 10px;
            text-decoration: none;
            border-radius: 4px;
            border: 0;
            color: #fefbef;
            font-family: 'Open Sans', sans-serif;
            font-weight: bold;
            line-height: 1;
            white-space: nowrap;
        }
    </style>
<table id="browser-warning-banner">
        <tr>
            <td class="image"><img src="/images/exclamation-triangle.gif"/></td>
            <td class="text"><span>Upgrade browser for full Crossref experience. It looks like you may be using an outdated web browser. Please update your browser for the best possible experience.</span></td>
            <td><a class="button" href="/supported-browsers.html" target="_blank" rel="noopener noreferrer">Supported Browsers</a></td>
        </tr>
    </table>
<![endif]--><!--
<br/>

<table border="0" cellpadding="0" cellspacing="0"><tr>

<td nowrap width="8" valign="top" class="tabSelected"><img src="/images/clips/top_left.gif" width="8" height="8" alt=""></td>
<td nowrap class="tabSelected"><a href="/servlet/useragent" title="" class="tabSelected">&nbsp;&nbsp;<b>Home</b>&nbsp;&nbsp;</a></td>
<td nowrap width="8" valign="top" class="tabSelected"><img src="/images/clips/top_right.gif" width="8" height="8" alt=""></td>

<td nowrap width="8" valign="top" class="tabNotAllowed"><img src="/images/clips/top_left.gif" width="8" height="8" alt=""></td>
<td nowrap class="tabNotAllowed"><a href="javascript:alert('You do not have permissions to access this function.')" title="Users: Not Accessible" class="tabNotAllowed">&nbsp;&nbsp;Users&nbsp;&nbsp;</a></td>
<td nowrap width="8" valign="top" class="tabNotAllowed"><img src="/images/clips/top_right.gif" width="8" height="8" alt=""></td>

<td nowrap width="8" valign="top" class="tabNotAllowed"><img src="/images/clips/top_left.gif" width="8" height="8" alt=""></td>
<td nowrap class="tabNotAllowed"><a href="javascript:alert('You do not have permissions to access this function.')" title="Submissions: Not Accessible" class="tabNotAllowed">&nbsp;&nbsp;Submissions&nbsp;&nbsp;</a></td>
<td nowrap width="8" valign="top" class="tabNotAllowed"><img src="/images/clips/top_right.gif" width="8" height="8" alt=""></td>

<td nowrap width="8" valign="top" class="tabNotAllowed"><img src="/images/clips/top_left.gif" width="8" height="8" alt=""></td>
<td nowrap class="tabNotAllowed"><a href="javascript:alert('You do not have permissions to access this function.')" title="Queries: Not Accessible" class="tabNotAllowed">&nbsp;&nbsp;Queries&nbsp;&nbsp;</a></td>
<td nowrap width="8" valign="top" class="tabNotAllowed"><img src="/images/clips/top_right.gif" width="8" height="8" alt=""></td>

<td nowrap width="8" valign="top" class="tabNotAllowed"><img src="/images/clips/top_left.gif" width="8" height="8" alt=""></td>
<td nowrap class="tabNotAllowed"><a href="javascript:alert('You do not have permissions to access this function.')" title="Reports: Not Accessible" class="tabNotAllowed">&nbsp;&nbsp;Reports&nbsp;&nbsp;</a></td>
<td nowrap width="8" valign="top" class="tabNotAllowed"><img src="/images/clips/top_right.gif" width="8" height="8" alt=""></td>

<td nowrap width="8" valign="top" class="tabNotAllowed"><img src="/images/clips/top_left.gif" width="8" height="8" alt=""></td>
<td nowrap class="tabNotAllowed"><a href="javascript:alert('You do not have permissions to access this function.')" title="Metadata Admin: Not Accessible" class="tabNotAllowed">&nbsp;&nbsp;Metadata Admin&nbsp;&nbsp;</a></td>
<td nowrap width="8" valign="top" class="tabNotAllowed"><img src="/images/clips/top_right.gif" width="8" height="8" alt=""></td>

</tr></table>

<table border="0" cellpadding="10" cellspacing="0" width="100%">
<tr><td width="100%" class="tabContent1">
<br>

-->

<!DOCTYPE html>
<html>
<head>
    <link rel=stylesheet href="https://test.crossref.org/css/tab.css" title="tab css">
    <link rel=stylesheet href="https://cdn.production.dcbridgecrossref.org/frontend/crossref-ui/2.1.1/crossref-ui.css" title="tab css">
    <link rel="shortcut icon" href="https://test.crossref.org/favicon.ico">
	<link href="https://cdn.jsdelivr.net/npm/@mdi/font@4.x/css/materialdesignicons.min.css" rel="stylesheet">
	<meta name="viewport" content="width=device-width, initial-scale=1, minimal-ui">
</head>
<!-- Matomo -->
<script type="text/x-template" id="template">
    <login-screen/>
</script>
<div id="app"></div>
<script type="text/javascript" src="https://cdn.production.dcbridgecrossref.org/frontend/crossref-ui/2.1.1/crossref-ui.umd.min.js"></script>
<script type="text/javascript">
var _paq = window._paq || [];
/* tracker methods like "setCustomDimension" should be called before "trackPageView" */
_paq.push(["setDocumentTitle", document.domain + "/" + document.title]);
_paq.push(["setCookieDomain", "*.apps.crossref.org"]);
_paq.push(['trackPageView']);
_paq.push(['enableLinkTracking']);
(function() {
var u="https://crossref.matomo.cloud/";
_paq.push(['setTrackerUrl', u+'matomo.php']);
_paq.push(['setSiteId', '15']);
var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
g.type='text/javascript'; g.async=true; g.defer=true; g.src=u+'matomo.js'; s.parentNode.insertBefore(g,s);
})();
var parts = window.location.href.split("/");
var c = CrossrefUI.run({
  element: '#app',
  reset_password_url: 'https://authenticator.crossref.org/reset-password/',
  template: '#template',
  authApiBaseUrl: parts[0] + "//" + parts[2],
  apiPort: null,
  loginUrl: '/servlet/login',
  rolesUrl: '/servlet/login',
  authFieldSpec: {
    username: 'usr',
    password: 'pwd'
  },
  authPostDataFormat: 'formData',
  disableMirage: true
})
</script>
<noscript><p>![](upload://xspAPEnjaGTMynnpZt5IwvyRs90.gif)</p></noscript>
<!-- End Matomo Code -->
<body>
</body>
</html>

```

I used this upload method about 2 years ago already and with success.

What is wrong? Does the user needs an additional right to post via https post?  
Am I using the wrong names or IDs?  
I am available for live testing if need be, please feel free to mail to arrange a time.

Thanks  
Herbert Barkmann  
BARKMANN software & services

> **[BARKMANN software & services - Startseite. ONIX Lösungen, ONIX Export,...](https://onixtools.de)**
>
> Die Startseite von BARKMANN software & services in Buchenbach.
> BARKMANN software & services in Buchenbach ist spezialisiert auf Software für Metadatenaustausch und Metadatenmanagement in Verlagswesen.
> Als Produkte werden ONIX Export...

---

<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:** [25 October 2021 21:29 UTC](https://community.crossref.org/t/depositing-doi-registration-xml-using-https-post/2181/3 "2021-10-25T21:29:05Z")

</div>

Hi Herbert,

We’ve had two other users report similar results fairly recently.

I’ve reported those to our technical team, and I’ll your example there as well. You can view the ticket to follow any progress there, and leave any additional comments there, if you create a gitlab account for yourself.

> **[Error in HTTPs POST submission results in source code for admin tool (#1467)...](https://gitlab.com/crossref/issues/-/issues/1467)**
>
> Background We've had two users report this behavior in the past week. Observed behavior...

So far, the other two examples could be worked around by correcting specific issues with their usernames, but you seem to be using the correct username, in a format that should work.

Beyond that, we’re still not sure why the response to the query is the html source code for our login page, rather than a legible error message of some sort.

Apologies for the inconvenience.

---

<div class="post-metadata">

**Author:** ![coelias](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/coelias/32/304_2.png) [@coelias](https://community.crossref.org/u/coelias)\
**Post date:** [9 November 2021 15:47 UTC](https://community.crossref.org/t/depositing-doi-registration-xml-using-https-post/2181/4 "2021-11-09T15:47:35Z")

</div>

I had a chat with Herbert,  
In the end the variable names (login\_id, login\_password) were wrong,

They must be login\_id and login\_passwd although I recommended the more standard ones usr and pwd.

---

<div class="post-metadata">

**Author:** ![phamvuphiho](https://avatars.discourse-cdn.com/v4/letter/p/d26b3c/32.png) [@phamvuphiho](https://community.crossref.org/u/phamvuphiho)\
**Post date:** [13 December 2021 06:37 UTC](https://community.crossref.org/t/depositing-doi-registration-xml-using-https-post/2181/7 "2021-12-13T06:37:38Z")

</div>

My problems were as follows:  
I use the OJS for the DOI and it works successfully.

1. However, when I deposit the article, the status is “Not Deposit”, 401 unauthorized error".

 ![image](https://us1.discourse-cdn.com/flex020/uploads/crossref/original/1X/91f393a07ccd82498a9250d09cd832acfe91ffef.png)

1. In the crossref, I cannot search for the doi I have created.

## DOI: [https://doi.org/10.54855/ijte2202011](https://doi.org/10.54855/ijte2202011)

## DOI: [https://doi.org/10.54855/ijte2202012](https://doi.org/10.54855/ijte2202012)

## DOI: [https://doi.org/10.54855/ijte2202013](https://doi.org/10.54855/ijte2202013)

In this case, what should I do?

Please help me to clarify these things.

Thank you

Best regards and Merry Christmas!

---

<div class="post-metadata">

**Author:** ![ifarley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/ifarley/32/44_2.png) [@ifarley](https://community.crossref.org/u/ifarley)\
**Post date:** [13 December 2021 22:07 UTC](https://community.crossref.org/t/depositing-doi-registration-xml-using-https-post/2181/8 "2021-12-13T22:07:17Z")

</div>

Hi @phamvuphiho,

Thanks for your message, and welcome to the community forum.

All three of your DOI examples have been registered with us as you can see if you resolve the DOIs:

1. [https://doi.org/10.54855/ijte220201](https://doi.org/10.54855/ijte220201)
2. [https://doi.org/10.54855/ijte2202012](https://doi.org/10.54855/ijte2202012)
3. [https://doi.org/10.54855/ijte2202013](https://doi.org/10.54855/ijte2202013)

The DOIs are also available in our APIs:  
XML API: [https://doi.crossref.org/search/doi?pid=support@crossref.org&format=unixsd&doi=10.54855%2Fijte220201](https://doi.crossref.org/search/doi?pid=support@crossref.org&format=unixsd&doi=10.54855%2Fijte220201)

REST API: [https://api.crossref.org/works/10.54855/ijte2202012?mailto=support@crossref.org](https://api.crossref.org/works/10.54855/ijte2202012?mailto=support@crossref.org)

My best,  
Isaac

---

<div class="post-metadata">

**Author:** ![sreekarthik](https://avatars.discourse-cdn.com/v4/letter/s/cc9497/32.png) [@sreekarthik](https://community.crossref.org/u/sreekarthik)\
**Post date:** [5 January 2022 06:15 UTC](https://community.crossref.org/t/depositing-doi-registration-xml-using-https-post/2181/10 "2022-01-05T06:15:20Z")

</div>

Am getting the same results while posting the data via HTTP post. Anyone, please help me how to resolve this issue.

---

<div class="post-metadata">

**Author:** ![pdavis](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/pdavis/32/981_2.png) [@pdavis](https://community.crossref.org/u/pdavis)\
**Post date:** [5 January 2022 10:54 UTC](https://community.crossref.org/t/depositing-doi-registration-xml-using-https-post/2181/11 "2022-01-05T10:54:33Z")

</div>

Hi @sreekarthik,

Can I ask for your username please and any further information on the errors you are getting and even the code you are sending to us (with passwords removed).

Thanks,  
Paul

---

<div class="post-metadata">

**Author:** ![sreekarthik](https://avatars.discourse-cdn.com/v4/letter/s/cc9497/32.png) [@sreekarthik](https://community.crossref.org/u/sreekarthik)\
**Post date:** [5 January 2022 13:04 UTC](https://community.crossref.org/t/depositing-doi-registration-xml-using-https-post/2181/12 "2022-01-05T13:04:16Z")

</div>

Am getting the below message

![](upload://xspAPEnjaGTMynnpZt5IwvyRs90.gif)

, success=1, statusCode=200}  
responseString:::

![](upload://xspAPEnjaGTMynnpZt5IwvyRs90.gif)

And my user name is : [srini@newgen.co](mailto:srini@newgen.co)

my http post code:  
try {

```
		post = new org.apache.http.client.methods.HttpPost(
				eachSpub.get("host") + "?operation=doDOICitUpload?login_id=" + eachSpub.get("username") + "?"
						+ "login_passwd=" + eachSpub.get("password"));

		post.setHeader("Accept", "image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*");

		post.setHeader("Content-Type", "multipart/form-data;boundary=---------------------------7d22911b10028e");

		post.setHeader("User-Agent", "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Q312461)");

		post.setHeader("Accept-Language", "en-us");

		post.setHeader("Content-Disposition", "form-data; name=fname" + "; filename=" + metaFileName);

		File file = new File(metaFile);

		FileEntity entity = new FileEntity(file);

		post.setEntity(entity);

		CloseableHttpResponse postresponse = client.execute(post);

		responseString = org.apache.http.util.EntityUtils.toString(postresponse.getEntity());

		responseObj = (HashMap<String, Object>) Utils.stringToMap(responseString);

		post.releaseConnection();

		responseObj.put("statusCode", postresponse.getStatusLine().getStatusCode());

		if (postresponse.getStatusLine().getStatusCode() == 200) {
			responseObj.put("response", responseString);
		} else {
			responseObj.put("response", "400 Bad Request error");
		}
		responseObj.put("success", 1);

		System.out.println("responseObj:::" + responseObj);
		System.out.println("responseString:::" + responseString);

		client.close();

	} catch (Exception e1) {
		responseObj.put("response", false);
		e1.printStackTrace();

	}
```

---

<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:** [5 January 2022 14:20 UTC](https://community.crossref.org/t/depositing-doi-registration-xml-using-https-post/2181/13 "2022-01-05T14:20:29Z")

</div>

Can you try submitting again with the username followed by a forward slash and then your organizational role (in your case that’s ‘adhw’)?

So, instead of just  
[srini@newgen.co](mailto:srini@newgen.co)

Use  
[srini@newgen.co](mailto:srini@newgen.co)/adhw

This is related to an open issue that our technical team is investigating. You can follow any progress on that here:

> **[Error in HTTPs POST submission results in source code for admin tool (#1467)...](https://gitlab.com/crossref/issues/-/issues/1467)**
>
> Background We've had two users report this behavior in the past week. Observed behavior...

If adding the role value isn’t sufficient, let us know, and we’ll add your example to that ticket.

---

<div class="post-metadata">

**Author:** ![sreekarthik](https://avatars.discourse-cdn.com/v4/letter/s/cc9497/32.png) [@sreekarthik](https://community.crossref.org/u/sreekarthik)\
**Post date:** [7 January 2022 10:43 UTC](https://community.crossref.org/t/depositing-doi-registration-xml-using-https-post/2181/14 "2022-01-07T10:43:19Z")

</div>

Thanks now its works like a charm

---

<div class="post-metadata">

**Author:** ![Nacho](https://avatars.discourse-cdn.com/v4/letter/n/7bcc69/32.png) [@Nacho](https://community.crossref.org/u/Nacho)\
**Post date:** [22 June 2022 09:39 UTC](https://community.crossref.org/t/depositing-doi-registration-xml-using-https-post/2181/15 "2022-06-22T09:39:56Z")

</div>

Hi,

I’m facing with the same problem. When I try to upload some DOI’s the server respond me with and error 401 Unauthorized)'. I’ve upgrade OJs and I have the same problem, also I tried to change the user name to the email/role but it give me the same error; untill some months ago I used only the role un the user and it worked.

Do you know how can I solved it?

Thanks for helping me

Best,  
Nacho

---

<div class="post-metadata">

**Author:** ![ifarley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/ifarley/32/44_2.png) [@ifarley](https://community.crossref.org/u/ifarley)\
**Post date:** [28 June 2022 01:16 UTC](https://community.crossref.org/t/depositing-doi-registration-xml-using-https-post/2181/16 "2022-06-28T01:16:11Z")

</div>

Hi @Nacho,

Thanks for your message! There are a couple of possibilities that might be causing this issue. Could you send us your DOI prefix and/or Crossref username to [support@crossref.org](mailto:support@crossref.org) so we can take a closer look?

Thanks in advance,  
Isaac

---

<div class="post-metadata">

**Author:** ![Nacho](https://avatars.discourse-cdn.com/v4/letter/n/7bcc69/32.png) [@Nacho](https://community.crossref.org/u/Nacho)\
**Post date:** [28 June 2022 07:23 UTC](https://community.crossref.org/t/depositing-doi-registration-xml-using-https-post/2181/17 "2022-06-28T07:23:50Z")

</div>

Hi @ifarley,

Thanks for your answer. In my desperation, I also write to Crossref and it’s a problem with membership and billing that we are dealing with them.

Thanks  
Nacho