Title: Autoryzacja JWT dla WP REST API
Author: tmeister
Published: <strong>2015-09-05</strong>
Last modified: 2026-02-18

---

Szukaj wtyczek

![](https://ps.w.org/jwt-authentication-for-wp-rest-api/assets/banner-772x250.jpg?
rev=3326023)

![](https://ps.w.org/jwt-authentication-for-wp-rest-api/assets/icon-256x256.jpg?
rev=3372068)

# Autoryzacja JWT dla WP REST API

 Autor: [tmeister](https://profiles.wordpress.org/tmeister/)

[Pobierz](https://downloads.wordpress.org/plugin/jwt-authentication-for-wp-rest-api.1.5.0.zip)

 * [Szczegóły](https://pl.wordpress.org/plugins/jwt-authentication-for-wp-rest-api/#description)
 * [Recenzje](https://pl.wordpress.org/plugins/jwt-authentication-for-wp-rest-api/#reviews)
 *  [Instalacja](https://pl.wordpress.org/plugins/jwt-authentication-for-wp-rest-api/#installation)
 * [Rozwój](https://pl.wordpress.org/plugins/jwt-authentication-for-wp-rest-api/#developers)

 [Wsparcie](https://wordpress.org/support/plugin/jwt-authentication-for-wp-rest-api/)

## Opis

This plugin seamlessly extends the WP REST API, enabling robust and secure authentication
using JSON Web Tokens (JWT). It provides a straightforward way to authenticate users
via the REST API, returning a standard JWT upon successful login.

### Key features of this free version include:

 * **Standard JWT Authentication:** Implements the industry-standard [RFC 7519](https://tools.ietf.org/html/rfc7519)
   for secure claims representation.
 * **Simple Endpoints:** Offers clear `/token` and `/token/validate` endpoints for
   generating and validating tokens.
 * **Configurable Secret Key:** Define your unique secret key via `wp-config.php`
   for secure token signing.
 * **Optional CORS Support:** Easily enable Cross-Origin Resource Sharing support
   via a `wp-config.php` constant.
 * **Developer Hooks:** Provides filters (`jwt_auth_expire`, `jwt_auth_token_before_sign`,
   etc.) for customizing token behavior.

JSON Web Tokens are an open, industry standard method for representing claims securely
between two parties.

For users requiring more advanced capabilities such as multiple signing algorithms(
RS256, ES256), token refresh/revocation, UI-based configuration, or priority support,
consider checking out **[JWT Authentication PRO](https://jwtauth.pro/?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=description_link_soft)**.

**Support and Requests:** Please use [GitHub Issues](https://github.com/Tmeister/wp-api-jwt-auth/issues).
For priority support, consider upgrading to [PRO](https://jwtauth.pro/?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=description_support_link).

### WYMAGANIA

#### WP REST API V2

Ta wtyczka została stworzona by rozszerzyć funkcjonalność wtyczki [WP REST API V2](https://github.com/WP-API/WP-API)
i oczywiście została zbudowana w oparciu o nią.

Więc, aby używać **wp-api-jwt-auth** potrzebujesz zainstalować i włączyć [WP REST API](https://github.com/WP-API/WP-API).

### PHP

**Minimalna wersja PHP: 7.4.0**

### PHP HTTP Authorization Header Enable

Most shared hosting providers have disabled the **HTTP Authorization Header** by
default.

To enable this option you’ll need to edit your **.htaccess** file by adding the 
following:

    ```
    RewriteEngine on
    RewriteCond %{HTTP:Authorization} ^(.*)
    RewriteRule ^(.*) - [E=HTTP_AUTHORIZATION:%1]
    ```

#### WPENGINE

For WPEngine hosting, you’ll need to edit your **.htaccess** file by adding the 
following:

    ```
    SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
    ```

See https://github.com/Tmeister/wp-api-jwt-auth/issues/1 for more details.

### KONFIGURACJA

### Configure the Secret Key

The JWT needs a **secret key** to sign the token. This **secret key** must be unique
and never revealed.

To add the **secret key**, edit your wp-config.php file and add a new constant called**
JWT_AUTH_SECRET_KEY**:

    ```
    define('JWT_AUTH_SECRET_KEY', 'your-top-secret-key');
    ```

You can generate a secure key from: https://api.wordpress.org/secret-key/1.1/salt/

**Looking for easier configuration?** [JWT Authentication PRO](https://jwtauth.pro/?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=config_secret_key_link)
allows you to manage all settings through a simple admin UI.

### Configure CORS Support

The **wp-api-jwt-auth** plugin has the option to activate [CORS](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing)
support.

To enable CORS Support, edit your wp-config.php file and add a new constant called**
JWT_AUTH_CORS_ENABLE**:

    ```
    define('JWT_AUTH_CORS_ENABLE', true);
    ```

Finally, activate the plugin within your wp-admin.

### Przestrzeń nazw i punkty końcowe

When the plugin is activated, a new namespace is added:

    ```
    /jwt-auth/v1
    ```

Also, two new endpoints are added to this namespace:

Endpoint | HTTP Verb
 _/wp-json/jwt-auth/v1/token_ | POST _/wp-json/jwt-auth/v1/
token/validate_ | POST

**Need more functionality?** [JWT Authentication PRO](https://jwtauth.pro/?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=endpoints_pro_note)
includes additional endpoints for token refresh and revocation.

### ZASTOSOWANIE

#### /wp-json/jwt-auth/v1/token

This is the entry point for JWT Authentication.

It validates the user credentials, _username_ and _password_, and returns a token
to use in future requests to the API if the authentication is correct, or an error
if authentication fails.

Sample Request Using AngularJS

    ```
    (function() {
      var app = angular.module('jwtAuth', []);

      app.controller('MainController', function($scope, $http) {
        var apiHost = 'http://yourdomain.com/wp-json';

        $http.post(apiHost + '/jwt-auth/v1/token', {
          username: 'admin',
          password: 'password'
        })
        .then(function(response) {
          console.log(response.data)
        })
        .catch(function(error) {
          console.error('Error', error.data[0]);
        });
      });
    })();
    ```

Success Response From The Server

    ```
    {
      "token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJodHRwOlwvXC9qd3QuZGV2IiwiaWF0IjoxNDM4NTcxMDUwLCJuYmYiOjE0Mzg1NzEwNTAsImV4cCI6MTQzOTE3NTg1MCwiZGF0YSI6eyJ1c2VyIjp7ImlkIjoiMSJ9fX0.YNe6AyWW4B7ZwfFE5wJ0O6qQ8QFcYizimDmBy6hCH_8",
      "user_display_name": "admin",
      "user_email": "admin@localhost.dev",
      "user_nicename": "admin"
    }
    ```

Error Response From The Server

    ```
    {
      "code": "jwt_auth_failed",
      "data": {
        "status": 403
      },
      "message": "Invalid Credentials."
    }
    ```

Once you get the token, you must store it somewhere in your application, e.g., in
a **cookie** or using **localStorage**.

From this point, you should pass this token with every API call.

Sample Call Using The Authorization Header With AngularJS

    ```
    app.config(function($httpProvider) {
      $httpProvider.interceptors.push(['$q', '$location', '$cookies', function($q, $location, $cookies) {
        return {
          'request': function(config) {
            config.headers = config.headers || {};
            // Assume that you store the token in a cookie
            var globals = $cookies.getObject('globals') || {};
            // If the cookie has the CurrentUser and the token
            // add the Authorization header in each request
            if (globals.currentUser && globals.currentUser.token) {
              config.headers.Authorization = 'Bearer ' + globals.currentUser.token;
            }
            return config;
          }
        };
      }]);
    });
    ```

The **wp-api-jwt-auth** plugin will intercept every call to the server and will 
look for the Authorization Header. If the Authorization header is present, it will
try to decode the token and will set the user according to the data stored in it.

If the token is valid, the API call flow will continue as normal.

**Przykładowe nagłówki**

    ```
    POST /resource HTTP/1.1
    Host: server.example.com
    Authorization: Bearer mF_s9.B5f-4.1JqM
    ```

### BŁĘDY

If the token is invalid, an error will be returned. Here are some sample errors:

**Nieprawidłowe dane uwierzytelniające**

    ```
    [
      {
        "code": "jwt_auth_failed",
        "message": "Invalid Credentials.",
        "data": {
          "status": 403
        }
      }
    ]
    ```

**Niewłaściwy podpis**

    ```
    [
      {
        "code": "jwt_auth_invalid_token",
        "message": "Signature verification failed",
        "data": {
          "status": 403
        }
      }
    ]
    ```

**Wygasły token**

    ```
    [
      {
        "code": "jwt_auth_invalid_token",
        "message": "Expired token",
        "data": {
          "status": 403
        }
      }
    ]
    ```

**Need advanced error tracking?** [JWT Authentication PRO](https://jwtauth.pro/?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=errors_pro_note)
offers enhanced error tracking and monitoring capabilities.

#### /wp-json/jwt-auth/v1/token/validate

This is a simple helper endpoint to validate a token. You only need to make a POST
request with the Authorization header.

**Valid Token Response**

    ```
    {
      "code": "jwt_auth_valid_token",
      "data": {
        "status": 200
      }
    }
    ```

### DOSTĘPNE ZACZEPY

The **wp-api-jwt-auth** plugin is developer-friendly and provides five filters to
override the default settings.

#### jwt_auth_cors_allow_headers

The **jwt_auth_cors_allow_headers** filter allows you to modify the available headers
when CORS support is enabled.

Wartość domyślna:

    ```
    'Access-Control-Allow-Headers, Content-Type, Authorization'
    ```

#### jwt_auth_not_before

The **jwt_auth_not_before** filter allows you to change the [**nbf**](https://tools.ietf.org/html/rfc7519#section-4.1.5)
value before the token is created.

Wartość domyślna:

    ```
    Creation time - time()
    ```

#### jwt_auth_expire

The **jwt_auth_expire** filter allows you to change the [**exp**](https://tools.ietf.org/html/rfc7519#section-4.1.4)
value before the token is created.

Wartość domyślna:

    ```
    time() + (DAY_IN_SECONDS * 7)
    ```

#### jwt_auth_token_before_sign

The **jwt_auth_token_before_sign** filter allows you to modify all token data before
it is encoded and signed.

Wartość domyślna:

    ```
    $token = array(
        'iss' => get_bloginfo('url'),
        'iat' => $issuedAt,
        'nbf' => $notBefore,
        'exp' => $expire,
        'data' => array(
            'user' => array(
                'id' => $user->data->ID,
            )
        )
    );
    ```

**Want easier customization?** [JWT Authentication PRO](https://jwtauth.pro/?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=hook_payload_pro_note)
allows you to add custom claims directly through the admin UI.

#### jwt_auth_token_before_dispatch

The **jwt_auth_token_before_dispatch** filter allows you to modify the response 
array before it is sent to the client.

Wartość domyślna:

    ```
    $data = array(
        'token' => $token,
        'user_email' => $user->data->user_email,
        'user_nicename' => $user->data->user_nicename,
        'user_display_name' => $user->data->display_name,
    );
    ```

#### jwt_auth_algorithm

The **jwt_auth_algorithm** filter allows you to modify the signing algorithm.

Domyślna wartość:

    ```
    $token = JWT::encode(
        apply_filters('jwt_auth_token_before_sign', $token, $user),
        $secret_key,
        apply_filters('jwt_auth_algorithm', 'HS256')
    );

    // ...

    $token = JWT::decode(
        $token,
        new Key($secret_key, apply_filters('jwt_auth_algorithm', 'HS256'))
    );
    ```

### JWT Authentication PRO

Elevate your WordPress security and integration capabilities with **JWT Authentication
PRO**. Building upon the solid foundation of the free version, the PRO version offers
advanced features, enhanced security options, and a streamlined user experience:

 * **Easy Configuration UI:** Manage all settings directly from the WordPress admin
   area.
 * **Token Refresh Endpoint:** Allow users to refresh expired tokens seamlessly 
   without requiring re-login.
 * **Token Revocation Endpoint:** Immediately invalidate specific tokens for enhanced
   security control.
 * **Customizable Token Payload:** Add custom claims to your JWT payload to suit
   your specific application needs.
 * **Granular CORS Control:** Define allowed origins and headers with more precision
   directly in the settings.
 * **Rate Limiting:** Protect your endpoints from abuse with configurable rate limits.
 * **Audit Logs:** Keep track of token generation, validation, and errors.
 * **Priority Support:** Get faster, dedicated support directly from the developer.

**[Upgrade to JWT Authentication PRO Today!](https://jwtauth.pro/?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=pro_section_cta)**

### Free vs. PRO Comparison

Here’s a quick look at the key differences:

 * **Basic JWT Authentication:** Included (Free), Included (PRO)
 * **Token Generation:** Included (Free), Included (PRO)
 * **Token Validation:** Included (Free), Included (PRO)
 * **Token Refresh Mechanism:** Not Included (Free), Included (PRO)
 * **Token Revocation:** Not Included (Free), Included (PRO)
 * **Token Management Dashboard:** Not Included (Free), Included (PRO)
 * **Analytics & Monitoring:** Not Included (Free), Included (PRO)
 * **Geo-IP Identification:** Not Included (Free), Included (PRO)
 * **Rate Limiting:** Not Included (Free), Included (PRO)
 * **Detailed Documentation:** Basic (Free), Comprehensive (PRO)
 * **Developer Tools:** Not Included (Free), Included (PRO)
 * **Premium Support:** Community via GitHub (Free), Priority Direct Support (PRO)

## Instalacja

### Używając kokpitu WordPressa

 1. W kokpicie, na podstronie Wtyczki, kliknij 'Dodaj nową’
 2. Wyszukaj 'jwt-authentication-for-wp-rest-api’
 3. Kliknij 'Instaluj teraz’
 4. Włącz wtyczkę w kokpicie na stronie zarządzania wtyczkami

### Przesyłanie w kokpicie WordPressa

 1. W kokpicie, na podstronie Wtyczki, kliknij 'Dodaj nową’
 2. Przejdź do obszaru 'Prześlij’
 3. Wybierz plik `jwt-authentication-for-wp-rest-api.zip` ze swojego komputera
 4. Kliknij 'Instaluj teraz’
 5. Włącz wtyczkę w kokpicie na stronie zarządzania wtyczkami

Please read our [configuration guide](https://wordpress.org/plugins/jwt-authentication-for-wp-rest-api/)
to set up the plugin properly.

## Najczęściej zadawane pytania

### Does this plugin support algorithms other than HS256?

The free version only supports HS256. For support for RS256, ES256, and other algorithms,
please consider [JWT Authentication PRO](https://jwtauth.pro/?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=faq_algorithms_link).

### Can I manage settings without editing wp-config.php?

The free version requires editing `wp-config.php`. [JWT Authentication PRO](https://jwtauth.pro/?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=faq_config_link)
provides a full settings UI within the WordPress admin.

### Is there a way to refresh or revoke tokens?

Token refresh and revocation features are available in [JWT Authentication PRO](https://jwtauth.pro/?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=faq_refresh_revoke_link).

### Where can I get faster support?

Priority support is included with [JWT Authentication PRO](https://jwtauth.pro/?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=faq_support_link).
For free support, please use the [GitHub issues tracker](https://github.com/Tmeister/wp-api-jwt-auth/issues).

### How secure is JWT authentication?

JWT authentication is very secure when implemented correctly. Make sure to use a
strong secret key and keep it confidential. [JWT Auth PRO](https://jwtauth.pro/?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=faq_security_link)
offers additional security features like rate limiting and token revocation.

## Recenzje

![](https://secure.gravatar.com/avatar/6a48ee7bcbf3b5f4df07d7f779d251e48331c9a3f597e00019211b42ff2b9894?
s=60&d=retro&r=g)

### 󠀁[Simple and Great](https://wordpress.org/support/topic/simple-and-great-235/)󠁿

 [hozayrayz](https://profiles.wordpress.org/hozayrayz/) 2026-02-23

I currently have the free version, and it’s great and simple to use. I never had
an issue with it.

![](https://secure.gravatar.com/avatar/4a8a6866d6ca04fe6576d447c08da5bcb1fea1bc9920f74a72f6367514c37b09?
s=60&d=retro&r=g)

### 󠀁[it’s just sales](https://wordpress.org/support/topic/its-just-sales/)󠁿

 [dorf](https://profiles.wordpress.org/dorf/) 2026-02-02

they make it confusing and confounding on purpose

![](https://secure.gravatar.com/avatar/f61118c4dfd2a2b1554e7858c566ce07602a0b4bdec277744226cc4154ee32ba?
s=60&d=retro&r=g)

### 󠀁[Works Very well & Paid support is great](https://wordpress.org/support/topic/works-very-well-paid-support-is-great/)󠁿

 [xmtek](https://profiles.wordpress.org/xmtek/) 2025-09-23

The support guy is not a non-techie, so the support was actually helpful! The plugin
works great and let me really extend the user system of my WP so it can act in a
auth/auth capacity for the services behind it.

![](https://secure.gravatar.com/avatar/2f2668f8a579b8959a15beafebc538f9ac52248938e7532289149cfbc103a72e?
s=60&d=retro&r=g)

### 󠀁[Great plugin!](https://wordpress.org/support/topic/costant-message-to-upgrade-to-pro/)󠁿

 [Mwale Kalenga](https://profiles.wordpress.org/mwalek/) 2025-05-15 3 odpowiedzi

I’ve been using the plugin for over year, it’s very good and user friendly! At some
point there was a constant message to upgrade, but that was fixed.

![](https://secure.gravatar.com/avatar/a078b8399059fa4e9085c2ac42a66d481a38b9aaea4e2b0b97062e0d858a00bc?
s=60&d=retro&r=g)

### 󠀁[Upgrade message cannot be removed from my site.](https://wordpress.org/support/topic/upgrade-message-cannot-be-removed-from-my-site/)󠁿

 [Bizberg Themes](https://profiles.wordpress.org/bizbergthemes/) 2025-05-15 1 odpowiedź

Upgrade message cannot be removed from my site.

![](https://secure.gravatar.com/avatar/44d8a4de61a3c1dfb3693744a271a3301a0dc84d32d9f3c4be0f38acd57a8040?
s=60&d=retro&r=g)

### 󠀁[Getting an Issue while generating a token at login time](https://wordpress.org/support/topic/getting-an-issue-while-generating-a-token-at-login-time/)󠁿

 [vaibhavk326](https://profiles.wordpress.org/vaibhavk326/) 2025-05-07 1 odpowiedź

Hi, actually I am trying to generate token at my login time using an wp_login hook
but i am unable to do so, can you provide me any way to do it. Tell me whether there
is any buildin function is there that I can use. add_action(’wp_login’, function(
$user_login, $user) {if (!user_can($user, 'dokandar’)) {return;} $response = wp_remote_post(
site_url(’/wp-json/jwt-auth/v1/token’), [ 'body’ => [ 'username’ => $user_login,'
password’ => 'YOUR_DEFAULT_PASSWORD_IF_AVAILABLE’, // Not ideal, see note below ],]);
if (is_wp_error($response)) { error_log(’Token request failed: ’ . $response->get_error_message());
return; } $body = json_decode(wp_remote_retrieve_body($response), true); if (!empty(
$body[’token’])) { update_user_meta($user->ID, 'vendor_jwt_token_key’, $body[’token’]);}
else { error_log(’JWT token missing: ’ . json_encode($body)); } }, 10, 2); I am 
using this thing but thing is password can’t be accessed directly in wordpress.

 [ Przeczytaj 53 recenzje ](https://wordpress.org/support/plugin/jwt-authentication-for-wp-rest-api/reviews/)

## Kontrybutorzy i deweloperzy

„Autoryzacja JWT dla WP REST API” jest oprogramowaniem open source. Poniższe osoby
miały wkład w rozwój wtyczki.

Zaangażowani

 *   [ tmeister ](https://profiles.wordpress.org/tmeister/)

[Przetłumacz wtyczkę “Autoryzacja JWT dla WP REST API” na swój język.](https://translate.wordpress.org/projects/wp-plugins/jwt-authentication-for-wp-rest-api)

### Interesuje cię rozwój wtyczki?

[Przeglądaj kod](https://plugins.trac.wordpress.org/browser/jwt-authentication-for-wp-rest-api/),
sprawdź [repozytorium SVN](https://plugins.svn.wordpress.org/jwt-authentication-for-wp-rest-api/)
lub czytaj [dziennik rozwoju](https://plugins.trac.wordpress.org/log/jwt-authentication-for-wp-rest-api/)
przez [RSS](https://plugins.trac.wordpress.org/log/jwt-authentication-for-wp-rest-api/?limit=100&mode=stop_on_copy&format=rss).

## Rejestr zmian

#### 1.5.0

 * Security: Updated dependencies to latest secure versions (deep-copy, php-parser,
   phpunit)
 * Feature: Smart upgrade prompts that appear based on actual plugin usage rather
   than immediately after installation
 * Feature: Usage-based notifications showing real token activity in the dashboard
   for more relevant upgrade recommendations
 * Improvement: Better first-time experience – new users won’t see upgrade prompts
   until they’ve had a chance to use the plugin
 * Fix: UTM tracking on upgrade links now works correctly to measure campaign effectiveness

#### 1.4.1

 * Enhancement: Updated lucide-react from 0.294.0 to 0.541.0 – Latest icon library
   improvements with new icons and performance optimizations
 * Enhancement: Updated tailwind-merge from 2.6.0 to 3.3.1 – Enhanced CSS utility
   merging capabilities for better styling performance
 * Enhancement: Updated react-syntax-highlighter from 15.6.1 to 15.6.3 – Bug fixes
   for code display components
 * Development: Updated ESLint to version 9.34.0 – Latest JavaScript linting capabilities
 * Development: Updated TypeScript ESLint to version 8.40.0 – Improved TypeScript
   code quality checks
 * Development: Updated Vite to version 7.1.3 – Faster build times and improved 
   development experience
 * Development: Updated Vitest to version 3.2.4 – Enhanced testing framework with
   better coverage reporting
 * Development: Added @usebruno/cli version 2.9.1 – API testing capabilities for
   development

#### 1.4.0

 * Feature: Live API Explorer – Interactive tool to test JWT endpoints directly 
   from admin dashboard with real API calls
 * Feature: Enhanced Configuration Dashboard – Real-time monitoring of system health
   and setup requirements
 * Feature: Modern Admin Interface – Complete redesign with React-based components
   for improved usability
 * Performance: Optimized dashboard loading by consolidating API calls into single
   endpoint
 * Performance: Faster configuration checks with streamlined status validation
 * Enhancement: Improved visual design with better text clarity and professional
   styling
 * Enhancement: Modular interface with organized dashboard sections for easier navigation

#### 1.3.8

 * Fix upsell notice bug, now it is show only one time

#### 1.3.7

 * Added PRO announcement

#### 1.3.6

 * Added Safeguard in enqueue_plugin_assets to Handle Null or Empty $suffix

#### 1.3.5

 * Notice: Add JWT Authentication Pro beta announcement notice.

#### 1.3.4

 * Naprawa: Pomiń każdy typ walidacji, gdy nagłówek autoryzacji nie jest okazicielem(
   Bearer).
 * Funkcja: Dodano stronę ustawień, aby udostępnić dane oraz dodać informacje o 
   wtyczce.

#### 1.3.3

 * Aktualizuj php-jwt do 6.4.0
 * Napraw ostrzeżenia php (https://github.com/Tmeister/wp-api-jwt-auth/pull/259)
 * Naprawa warunku w którym sprawdzane jest, czy zapytanie jest zapytaniem REST (
   https://github.com/Tmeister/wp-api-jwt-auth/pull/256)

#### 1.3.2

 * Napraw konflikty z innymi wtyczkami które używają tej samej biblioteki JWT, dodając
   do klasy JWT przestrzeń nazw.

#### 1.3.1

 * Aktualizacja minimalnej wersji PHP do wersji 7.4
 * Waliduj algorytm podpisywania względem wspieranych algorytmów @zobacz https://
   www.rfc-editor.org/rfc/rfc7518#section-3
 * Zdezynfekuj wartości REQUEST_URL oraz HTTP_AUTHORIZATION przed wykorzystaniem
 * Użyj get_header() zamiast $_SERVER do pobrania nagłówka autoryzacji, jeśli to
   możliwe.
 * Dodano wpisane właściwości do klasy JWT_Auth tam, gdzie było to możliwe
 * Razem z tym wydaniem, wydaję do celów testowych nowego prostego klienta JWP Client
   App @zobacz https://github.com/Tmeister/jwt-client

#### 1.3.0

 * Zaktualizuj firebase/php-jwt do wersji 6.3
 * Napraw ostrzeżenie, register_rest_route zostało wywołane niepoprawnie
 * Pozwól na podstawowe uwierzytelnienie (Basic Auth) poprzez zaniechanie prób walidacji
   nagłówków autentykacji (Authentication Headers) jeśli adekwatny użytkownik został
   już określony (zobacz: https://github.com/Tmeister/wp-api-jwt-auth/issues/241)
 * Dodano nowy filtr (jwt_auth_algorithm), aby umożliwić dostosowanie algorytmu 
   używanego do podpisywania tokena
 * Props: https://github.com/bradmkjr

#### 1.2.6

 * Zgodność plików cookies z tokenem
 * Naprawiono źródło problemu z Gutenbergiem, nieskończoną pętlą, i udostępniono
   możliwość generowania/sprawdzania tokenu w sytuacji gdy istnieje WP cookie
 * Więcej informacji (https://github.com/Tmeister/wp-api-jwt-auth/pull/138)
 * Props: https://github.com/andrzejpiotrowski

#### 1.2.5

 * Dodano kompatybilność z Gutenbergiem
 * Więcej informacji (https://github.com/Tmeister/wp-api-jwt-auth/issues/126)

#### 1.2.4

 * Zaktualizowano firebase/php-jwt do v5.0.0 ( https://github.com/firebase/php-jwt)
 * Dodano tag 'Requires PHP’

#### 1.2.3

 * Napraw błąd rekurencji w WordPress 4.7 #44

#### 1.2.2

 * Dodaj dodatkowe sprawdzanie poprawności, aby uzyskać nagłówek autoryzacji
 * Podniesiono priorytet determine_current_user Rozwiązuje problem #13
 * Dodano obiekt użytkownika jako parametr do zaczepu jwt_auth_token_before_sign
 * Poprawiono komunikaty błędów przy niepowodzeniu autoryzacji #34
 * Przetestowano z 4.6.1

#### 1.2.0

 * Przetestowano z 4.4.2

#### 1.0.0

 * Pierwsze wydanie.

## Meta

 *  Wersja **1.5.0**
 *  Ostatnia aktualizacja **2 miesiące temu**
 *  Włączone instalacje **60 000+**
 *  Wersja WordPressa ** 4.2 lub nowszej **
 *  Testowano do **6.9.4**
 *  Wersja PHP ** 7.4.0 lub nowszej **
 *  Język
 * [English (US)](https://wordpress.org/plugins/jwt-authentication-for-wp-rest-api/)
 * Tagi
 * [json web authentication](https://pl.wordpress.org/plugins/tags/json-web-authentication/)
   [jwt](https://pl.wordpress.org/plugins/tags/jwt/)[oauth](https://pl.wordpress.org/plugins/tags/oauth/)
   [rest-api](https://pl.wordpress.org/plugins/tags/rest-api/)[wp-api](https://pl.wordpress.org/plugins/tags/wp-api/)
 *  [Widok zaawansowany](https://pl.wordpress.org/plugins/jwt-authentication-for-wp-rest-api/advanced/)

## Oceny

 4.4 na 5 gwiazdek.

 *  [  42 recenzje 5-gwiazdkowe     ](https://wordpress.org/support/plugin/jwt-authentication-for-wp-rest-api/reviews/?filter=5)
 *  [  2 recenzje 4-gwiazdkowe     ](https://wordpress.org/support/plugin/jwt-authentication-for-wp-rest-api/reviews/?filter=4)
 *  [  2 recenzje 3-gwiazdkowe     ](https://wordpress.org/support/plugin/jwt-authentication-for-wp-rest-api/reviews/?filter=3)
 *  [  1 recenzja 2-gwiazdkowa     ](https://wordpress.org/support/plugin/jwt-authentication-for-wp-rest-api/reviews/?filter=2)
 *  [  6 recenzji 1-gwiazdkowych     ](https://wordpress.org/support/plugin/jwt-authentication-for-wp-rest-api/reviews/?filter=1)

[Your review](https://wordpress.org/support/plugin/jwt-authentication-for-wp-rest-api/reviews/#new-post)

[Zobacz wszystkierecenzje.](https://wordpress.org/support/plugin/jwt-authentication-for-wp-rest-api/reviews/)

## Zaangażowani

 *   [ tmeister ](https://profiles.wordpress.org/tmeister/)

## Wsparcie

Masz coś do dodania? Potrzebujesz pomocy?

 [Zobacz forum wsparcia](https://wordpress.org/support/plugin/jwt-authentication-for-wp-rest-api/)

## Złóż datek

Czy chcesz wesprzeć rozwój wtyczki?

 [ Wspomóż wtyczkę ](https://github.com/sponsors/Tmeister)