API:Account creation/pre-1.27/tr

From MediaWiki.org
Jump to navigation Jump to search

Hesap oluşturma[edit]

API'yi kullanarak hesaplar oluşturabilirsiniz. Bu, kendiniz için yeni bir hesap olabilir veya başka birine, o kişiye rastgele bir parola göndererek bir hesap oluşturabilirsiniz. Hesap kreasyonları Special:log/newusers içine kaydedilir. Giriş yaptıysanız, bir hesap oluştururken kullanıcı adınız da kaydedilecektir.

Parametreler[edit]

  • name: Kullanıcı adı.
  • password: Parola (mailpassword ayarlanmışsa yoksayılır).
  • domain: Harici kimlik doğrulama alanı.
  • token: İlk istekte hesap oluşturma anahtarı alındı.
  • email: Kullanıcının e-posta adresi (mailpassword veya $wgEmailConfirmToEdit ayarlanmışsa gereklidir).
  • realname: Kullanıcının gerçek adı. Birçok vikide $wgHiddenPrefs aracılığıyla realname devre dışıdır. realname etkin olup olmadığını kontrol etmek için api.php?action=query&meta=userinfo&uiprop=realname isteyin. Yanıtta realname özelliği almazsanız, realname gizli bir tercihtir.
  • mailpassword: Herhangi bir değere ayarlanırsa, rastgele bir parola oluşturulur ve kullanıcıya e-posta ile gönderilir (password parametresini kullanmak yerine).
  • reason: Hesap oluşturma nedeni. Hesap oluşturma günlüğünde gösterilecek (örnek).
  • language: Kullanıcı için varsayılan olarak ayarlanacak dil kodu.

Extension:ConfirmEdit ile kullanıldığında genişletilmiş parametreler (ReCaptcha hariç):

  • captchaid: Daha önce captcha gerekiyorsa, izleme isteği ile göndermek için CAPTCHA Kimliği sağlanmıştır.
  • captchaword: Captcha gerekiyorsa, takip isteği ile göndermek için CAPTCHA'nın kullanıcı tarafından sağlanan yanıtı.

Anahtar[edit]

Bir hesap oluşturmak için bir anahtar gereklidir. Bir belirteç almak için, belirteç alanının boş bir dize olması dışında istediğiniz isteği yaparsınız. Jetonu aldıktan sonra, istek doldurularak tekrar istekte bulunursunuz. Bu oturum açma modülünün çalışma şekline benzer. Ayrıntılar için aşağıdaki örneğe bakın.

Çoğu API Anahtarının aksine, hesap belirteçleri oluşturma yalnızca bir istek için çalışır. Bu modülle bir hesap oluşturduktan sonra, başka bir hesap oluşturmadan önce yeni bir anahtara ihtiyacınız var (Başarı mesajı böyle bir anahtar içerecektir)

Örnek[edit]

Not: Bu örnekte, tüm parametreler sadece basitlik amacıyla bir GET isteğinde iletilir. Ancak, action=createaccount POST istekleri gerektirir; GET istekleri hataya neden olur.

Adım 1: GymBeauWhales için bir hesap oluşturmak için anahtarı alın

Şimdi şöyle bir yanıt almalıyız:

{
    "createaccount": {
        "result": "NeedToken", 
        "token": "387bc54bd0ec29333178800ce4213306"
    }
}
"newcookiesfornew" ile ilgili bir hata alırsanız, bunun nedeni 1.21'in ilk sürümlerindeki bir hatadır. İsteğin tekrarlanması sorunu çözmelidir

Burada verilen anahtarı alıp isteğe ekliyoruz:

Adım 2: Aslında GymBeauWhales hesabı oluşturun

Her şeyin işe yaradığını varsayarsak, şöyle bir sonuç almalıyız:

{
    "createaccount": {
        "result": "Success", 
        "token": "387bc54bd0ec29333178800ce4213306", 
        "userid": 1234, 
        "username": "GymBeauWhales"
    }
}

And GymBeauWhales@example.com would get an email with instructions on how to log in.

CAPTCHA[edit]

When used with Extension:ConfirmEdit, a CAPTCHA may be presented for new account creations. This is supported via extension in the API here.

When submitting per the above rules and receiving a response, you may also receive a captcha node in the return data, similar to what is sometimes returned by action=edit.

For a text-based CAPTCHA:

{
  "createaccount": {
    "result": "NeedCaptcha",
    "captcha": {
      "type": "simple",
      "mime": "text/plain",
      "id": "323035635",
      "question": "77+5"
    }
  }
}

For an image-based CAPTCHA:

{
  "createaccount": {
    "result": "NeedCaptcha",
    "captcha": {
      "type": "image",
      "mime": "image/png",
      "id": "1147869849",
      "url": "/core/index.php?title=Special:Captcha/image&wpCaptchaId=1147869849"
    }
  }
}

Be aware that the URL may be site-relative or protocol-relative.

When you receive such a response, you need to submit a third response, which is similar to the one submitted in step 2 but contains the necessary responses. By default, you should return the captcha id in the captchaid parameter, and the value (solution) of the captcha in the captchaword parameter, however some captcha modules, like ReCaptcha, use different parameters. Check the module's documentation for specifics.

As of the current code (see [1]) you won't receive the captcha prompt response until after basic validation errors have been taken care of.

Possible outputs[edit]

The result value can have one of three values (n.b., values are lower-case prior to 1.23):

  • NeedToken: A token is needed. A token parameter should also be set with a token to use.
    { "createaccount": { "result": "NeedToken", "token": "8217b293a6bd0bba84cc1cb661a06a5d" } }
    
    • If you get a NeedToken result when you are expecting a success result, make sure the token you are sending is correct, and that you are sending along any cookies sent by the API.
  • Success: Everything worked
    { "createaccount": { "result": "Success", "token": "8217b293a6bd0bba84cc1cb661a06a5d", "userid": 1234, "username": "Foo" } }
    
  • Warning: Not used in core, however extensions can (in theory) add warnings, in which case the result attribute will be warning. However, this still generally means the account was created successfully.

Possible errors[edit]

All errors are formatted as:

{
    "error": {
        "code": "code", 
        "info": "info"
    }
}

Many of the info codes to this module correspond to system messages. As a result the info part may change and in particular will vary with language.

Code Info
nocookiesfornew The user account was not created, as we could not confirm its source. Ensure you have cookies enabled, reload this page and try again.
Note: This code is sometimes returned due to a bug in early versions of MediaWiki 1.21. If you receive this error, retrying the request (ensuring cookies are sent) should fix.
sorbs_create_account_reason Your IP address is listed as an open proxy in the DNSBL .
noname You have not specified a valid username
userexists Username entered already in use
password-name-match Your password must be different from your username.
password-login-forbidden The use of this username and password has been forbidden
noemailtitle No email address
invalidemailaddress The e-mail address cannot be accepted as it appears to have an invalid format
externaldberror There was either an authentication database error or you are not allowed to update your external account
passwordtooshort The password was shorter than the value of $wgMinimalPasswordLength
noemail There is no e-mail address recorded for user
mustbeposted The createaccount module requires a POST request
acct_creation_throttle_hit Visitors to this wiki using your IP address have created $1 accounts in the last day, which is the maximum allowed in this time period. As a result, visitors using this IP address cannot create any more accounts at the moment.
wrongpassword Incorrect password entered. Please try again.
Note: Can be caused by the "domain" field being incorrect.
aborted Aborted by an extension (info will have more details)
blocked You cannot create a new account because you are blocked
permdenied-createaccount You do not have the right to create a new account
createaccount-hook-aborted An extension aborted the account creation
captcha-createaccount-fail (With Extension:ConfirmEdit and old core) Submitted CAPTCHA answer was incorrect

Disable[edit]

To disable specifically this API feature, insert the following line in your configuration file:

$wgAPIModules['createaccount'] = 'ApiDisabled';

See also[edit]



action=createaccount (create)

(main | createaccount)
  • This module requires write rights.
  • This module only accepts POST requests.
  • Source: MediaWiki
  • License: GPL-2.0-or-later

Create a new user account.

The general procedure to use this module is:

  1. Fetch the fields available from action=query&meta=authmanagerinfo with amirequestsfor=create, and a createaccount token from action=query&meta=tokens.
  2. Present the fields to the user, and obtain their submission.
  3. Post to this module, supplying createreturnurl and any relevant fields.
  4. Check the status in the response.
    • If you received PASS or FAIL, you're done. The operation either succeeded or it didn't.
    • If you received UI, present the new fields to the user and obtain their submission. Then post to this module with createcontinue and the relevant fields set, and repeat step 4.
    • If you received REDIRECT, direct the user to the redirecttarget and wait for the return to createreturnurl. Then post to this module with createcontinue and any fields passed to the return URL, and repeat step 4.
    • If you received RESTART, that means the authentication worked but we don't have a linked user account. You might treat this as UI or as FAIL.
Parameters:
createrequests

Only use these authentication requests, by the id returned from action=query&meta=authmanagerinfo with amirequestsfor=create or from a previous response from this module.

Separate values with | or alternative.
Maximum number of values is 50 (500 for clients allowed higher limits).
createmessageformat

Format to use for returning messages.

One of the following values: html, none, raw, wikitext
Default: wikitext
createmergerequestfields

Merge field information for all authentication requests into one array.

Type: boolean (details)
createpreservestate

Preserve state from a previous failed login attempt, if possible.

If action=query&meta=authmanagerinfo returned true for hasprimarypreservedstate, requests marked as primary-required should be omitted. If it returned a non-empty value for preservedusername, that username must be used for the username parameter.

Type: boolean (details)
createreturnurl

Return URL for third-party authentication flows, must be absolute. Either this or createcontinue is required.

Upon receiving a REDIRECT response, you will typically open a browser or web view to the specified redirecttarget URL for a third-party authentication flow. When that completes, the third party will send the browser or web view to this URL. You should extract any query or POST parameters from the URL and pass them as a createcontinue request to this API module.

createcontinue

This request is a continuation after an earlier UI or REDIRECT response. Either this or createreturnurl is required.

Type: boolean (details)
createtoken

A "createaccount" token retrieved from action=query&meta=tokens

This parameter is required.
*
This module accepts additional parameters depending on the available authentication requests. Use action=query&meta=authmanagerinfo with amirequestsfor=create (or a previous response from this module, if applicable) to determine the requests available and the fields that they use.