![]() It will report invalid values and suggest fixes in case error was possibly due to a typo: 15:50:06.800 Failed to start ejabberd application: Invalid value of option modules->mod_pubsub->plugins: unexpected value: pepp. More generally, it can check value against expected types: 15:51:34.007 Failed to start ejabberd application: Invalid value of option modules->mod_roster->versioning: expected boolean, got string instead In the following example, the validator will check against a value range: 14:15:48:32.582 Failed to start ejabberd application: Invalid value of option loglevel: expected integer from 0 to 5, got: 6 Here are a couple of examples of the kind of message that the new configuration validator can produce. The configuration will either be fully reloaded or rolled back. If the suffix is not given, the timeout is assumed in seconds Atomic configuration reload Now, all timeout values can be expanded with suffixes, e.g. There is not need to quote string to express the fact you want an atom in the configuration file: the new configuration validator handles the Erlang types mapping automatically. ![]() For example, it supports the following: Better handling of Erlang atom vs string The new configuration validator makes it possible to improve the configuration parsing. This configuration checker has also been released as an independent open source project: yconf. With ejabberd 19.08, we introduce a new configuration checker, giving more precise configuration guidance in case of syntax errors or misconfiguration. Now, the user can use this token as a password before 1774546510 epoch time (i.e. Authenticate on XMPP using encoded token as password This encoded token is the password that can use to login in ejabberd. In Verify signature, replace “your-256-bit-secret” with the content of “k” in previous page.Į6mricARxecpKOmte0uDjEpcFwwHwwdzYF7TM0KijJ4.See jwt.io for an example of how to generate JSON Web Tokens. In ejabberd.yml change auth_method to jwt and add the jwt_key option pointing to secret.jwk: auth_method: jwt With that key, you can generate credentials for any users on your server. secret.jwk.īe careful: This key must never be shared or committed anywhere. "k": "cjjkgwWy64_olK22FaABFblB2d-L4kXC2TsTZ4ixxoyMh1wMNhwc3WbWfJsZV6OvVNesd2Xx4PQoOa_YX-g1EyHbNWPzDA8ptAXaBxBUjqtQHN9pEAly4HC9I3h1iQv8yKjj9h-dqCk10Z6aOZ0jxseBR0X-yPqsrzMKAw6_IFTeoEe-hiQwhpPR5XKitN3bJTCo5oZ_EKqRwWQ5pQ0He-Z4Iis2C1j2QlRf_0vWpbw5MsnUW3kEoLvPj2exFLuKKbsImzMeayIfuduQ4WJcgadYWvFlX3SU9mDmXLUWmHBYdTo5ip76uLHB3F3XAHAqeta5oeLqw7vopDPUyZMGMw", To generate a JSON Web Key, you can for example use JSON Web Key Generator, or use your own local tool for production deployment.Įxample using : in that page, the oct tab, select: You need to generate a secret key to be able to sign your JWT tokens. This feature allows you to have your backend generate authentication tokens with a limited lifetime. You can now authenticate with JSON Web Token (JWT, see jwt.io for details). New Features and improvements New authentication method using JWT tokens As usual, we have kept on improving server performance and fixed several issues. The main focus has been to further improve ease of use, consistency, performance, but also to start cleaning up our code base. We are pleased to announce ejabberd version 19.08.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |