Table of Contents

Function

The AuthInfo1Create task requests an AuthInfo1.

If a cancelation of the Preack task exists, you cannot generate an AuthInfo1 yourself via the system. In this case, the system generates AuthInfo1 automatically. For the execution types "now" and "date", the AuthInfo is then valid for 30 days from the cancelation date (execdate). If the execution date "expire" is selected, that is, the termination on the expiration date, the AuthInfo is valid from 30 days before the expiration date.

Description

Route: POST /domain/{name}/_authinfo1
No body has to be sent.

Request 
{
}
Response 
{
  "status": {
    "code": "S0113001",
    "text": "AuthInfo1 was created successfully.",
    "type": "SUCCESS"
  },
  "object": {
    "type": "Domain",
    "value": "example.com"
  }
}

Task code: 0113001
Uses Domain object

Successful creation of the AuthInfo

Request 
<request>
	<auth>
		<user>customer</user>
		<password>password</password>
		<context>4</context>
	</auth>
	<owner>
		<user>customer2</user>
		<context>4</context>
	</owner>
	<task>
		<code>0113001</code>
		<domain>
			<name>example.com</name>
		</domain>
	</task>
</request>
Response 
<response>
	<result>
		<data/>
		<status>
			<code>S0113001</code>
			<text>AuthInfo1 was created successfully.</text>
			<type>success</type>
			<object>
				<type>authinfo</type>
				<value>kiSV/CbJi9/KaCxp</value>
			</object>
		</status>
	</result>
</response>

Response if an AuthInfo already exists

Response 
<response>
	<result>
		<data />
		<msg>
			<code>EF011316</code>
			<type>error</type>
			<object>
				<type>authinfo</type>
				<value></value>
			</object>
		</msg>
		<status>
			<code>E0113001</code>
			<text>AuthInfo1 could not be created.</text>
			<type>error</type>
			<object>
				<type>authinfo</type>
				<value>12345-abcd</value>
			</object>
		</status>
	</result>
</response>
  • No labels