Mercurial > prosody-modules
annotate mod_log_messages_sql/README.markdown @ 5264:d3ebaef1ea7a
mod_http_oauth2: Correctly verify OAuth client credentials on revocation
Makes no sense to validate against username and password here, or using
a token to revoke another token, or itself?
In fact, upon further discussion, why do you need credentials to revoke
a token? If you are not supposed to have the token, revoking it seems
the most responsible thing to do with it, so it should be allowed, while
if you are supposed to have it, you should be allowed to revoke it.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 21 Mar 2023 21:57:18 +0100 |
parents | b74c86d137c9 |
children |
rev | line source |
---|---|
2406
a216be9b1d6e
mod_log_messages_sql/README: Point out incompatibility with 0.10
Kim Alvefur <zash@zash.se>
parents:
2323
diff
changeset
|
1 # Introduction |
a216be9b1d6e
mod_log_messages_sql/README: Point out incompatibility with 0.10
Kim Alvefur <zash@zash.se>
parents:
2323
diff
changeset
|
2 |
3438
b74c86d137c9
mod_log_messages_sql/README: Add pointer towards mod_mam + mod_readonly
Kim Alvefur <zash@zash.se>
parents:
2406
diff
changeset
|
3 ::: {.alert .alert-danger} |
b74c86d137c9
mod_log_messages_sql/README: Add pointer towards mod_mam + mod_readonly
Kim Alvefur <zash@zash.se>
parents:
2406
diff
changeset
|
4 Consider using [mod_mam][doc:modules:mod_mam] together with |
b74c86d137c9
mod_log_messages_sql/README: Add pointer towards mod_mam + mod_readonly
Kim Alvefur <zash@zash.se>
parents:
2406
diff
changeset
|
5 [mod_readonly] instead. |
b74c86d137c9
mod_log_messages_sql/README: Add pointer towards mod_mam + mod_readonly
Kim Alvefur <zash@zash.se>
parents:
2406
diff
changeset
|
6 ::: |
b74c86d137c9
mod_log_messages_sql/README: Add pointer towards mod_mam + mod_readonly
Kim Alvefur <zash@zash.se>
parents:
2406
diff
changeset
|
7 |
2323 | 8 This module logs messages to a SQL database. |
9 | |
10 SQL connection options are configured in a `message_log_sql` option, | |
11 which has the same syntax as the `sql` option for | |
12 [mod_storage_sql][doc:modules:mod_storage_sql]. | |
13 | |
2406
a216be9b1d6e
mod_log_messages_sql/README: Point out incompatibility with 0.10
Kim Alvefur <zash@zash.se>
parents:
2323
diff
changeset
|
14 # Usage |
a216be9b1d6e
mod_log_messages_sql/README: Point out incompatibility with 0.10
Kim Alvefur <zash@zash.se>
parents:
2323
diff
changeset
|
15 |
2323 | 16 You will need to create the following table in the configured database: |
17 | |
18 ``` sql | |
19 CREATE TABLE `prosodyarchive` ( | |
20 `host` TEXT, | |
21 `user` TEXT, | |
22 `store` TEXT, | |
23 `id` INTEGER PRIMARY KEY AUTOINCREMENT, | |
24 `when` INTEGER, | |
25 `with` TEXT, | |
26 `resource` TEXT, | |
27 `stanza` TEXT); | |
28 ``` | |
2406
a216be9b1d6e
mod_log_messages_sql/README: Point out incompatibility with 0.10
Kim Alvefur <zash@zash.se>
parents:
2323
diff
changeset
|
29 |
a216be9b1d6e
mod_log_messages_sql/README: Point out incompatibility with 0.10
Kim Alvefur <zash@zash.se>
parents:
2323
diff
changeset
|
30 # Compatibility |
a216be9b1d6e
mod_log_messages_sql/README: Point out incompatibility with 0.10
Kim Alvefur <zash@zash.se>
parents:
2323
diff
changeset
|
31 |
a216be9b1d6e
mod_log_messages_sql/README: Point out incompatibility with 0.10
Kim Alvefur <zash@zash.se>
parents:
2323
diff
changeset
|
32 Does *NOT* work with 0.10 due to a conflict with the new archiving |
a216be9b1d6e
mod_log_messages_sql/README: Point out incompatibility with 0.10
Kim Alvefur <zash@zash.se>
parents:
2323
diff
changeset
|
33 support in `mod_storage_sql`ยท |