<a id="qiita"></a>

# Qiita

<a id="backend-class"></a>

## Backend class

For Django, add this class path to `AUTHENTICATION_BACKENDS`. For other
integrations, use the same class path in the framework-specific backend
setting.

| Backend name   | Class path                               |
|----------------|------------------------------------------|
| `qiita`        | `social_core.backends.qiita.QiitaOAuth2` |

Qiita

- Register a new application at [Qiita](https://qiita.com/settings/applications), set the callback URL to
  `http://example.com/complete/qiita/` replacing `example.com` with your
  domain.
- Fill `Client ID` and `Client Secret` values in the settings:
  ```default
  SOCIAL_AUTH_QIITA_KEY = ''
  SOCIAL_AUTH_QIITA_SECRET = ''
  ```
- Also it’s possible to define extra permissions with:
  ```default
  SOCIAL_AUTH_QIITA_SCOPE = [...]
  ```

  See auth scopes at [Qiita Scopes docs](https://qiita.com/api/v2/docs#スコープ).
- Users are identified by the stable `permanent_id`. Associations created by
  older social-core releases used the renameable `id` and migrate on the next
  successful authentication. The following legacy setting remains accepted,
  but no longer changes the default:
  ```default
  SOCIAL_AUTH_QIITA_IDENTIFIED_BY_PERMANENT_ID = True
  ```
