# Kibana 7.10 login issues

**URL:** https://discuss.elastic.co/t/kibana-7-10-login-issues/255201
**Category:** Kibana
**Tags:** elastic-stack-security
**Created:** [November 12, 2020, 11:05am UTC](https://discuss.elastic.co/t/kibana-7-10-login-issues/255201 "2020-11-12T11:05:18Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)
#### Post date: [November 12, 2020, 1:45pm UTC](https://discuss.elastic.co/t/kibana-7-10-login-issues/255201/3 "2020-11-12T13:45:34Z")

</div>

Hey @KevSex,

Yeah, as @flash1293 already noted, it's an internal API and we reserve the right to make any breaking changes to it even though we try hard to not do that without a strong need.

Back to your original question, [here is the definition](https://github.com/elastic/kibana/blob/v7.10.0/x-pack/plugins/security/server/routes/authentication/common.ts#L122-L135) of request body schema:

```auto
schema.object({
  providerType: schema.string(),
  providerName: schema.string(),
  currentURL: schema.string(),
  params: schema.conditional(
    schema.siblingRef('providerType'),
    schema.oneOf([
      schema.literal(BasicAuthenticationProvider.type),
      schema.literal(TokenAuthenticationProvider.type),
    ]),
    basicParamsSchema,
    schema.never()
  ),
}),

```

So assuming you're using default `xpack.security.autch.providers` config, your request should look like this:

```auto
POST https://localhost:5601/internal/security/login
Accept: application/json
Content-Type: application/json
kbn-xsrf: true

{
  "providerType": "basic",
  "providerName": "basic",
  "currentURL": "/",
  "params": { "username": " ***", "password": "***" }
}

```

`providerName` is an arbitrary string and depends on how you configure Kibana, you can read more about this [here](https://www.elastic.co/guide/en/kibana/current/security-settings-kb.html#authentication-security-settings).

We changed the API signature so that it can work with all authentication mechanisms Kibana supports now or will in the future.

Let me know if you have any other questions.

Best,  
Oleg

---

_[View the full topic](https://discuss.elastic.co/t/kibana-7-10-login-issues/255201)._