complements authentication changes

pull/320/head
msramalho 2025-06-17 12:54:43 +01:00
rodzic 7ab804d163
commit 1b6d85884b
Nie znaleziono w bazie danych klucza dla tego podpisu
1 zmienionych plików z 3 dodań i 3 usunięć

Wyświetl plik

@ -9,8 +9,8 @@ There are two main use cases for authentication:
```{note} ```{note}
The Authentication framework currently only works with the following modules: The Authentication framework currently only works with the following modules:
* Generic Extractor * [Generic Extractor](../modules/autogen/extractor/generic_extractor.md) - the main module for extracting content from websites
* Screenshot Enricher * [Antibot Extractor/Enricher](../modules/autogen/extractor/antibot_extractor_enricher.md)
To authenticate for WACZ archiving, see the instructions on the [](../modules/autogen/enricher/wacz_extractor_enricher.md) page. To authenticate for WACZ archiving, see the instructions on the [](../modules/autogen/enricher/wacz_extractor_enricher.md) page.
``` ```
@ -34,7 +34,7 @@ You can save your authentication information directly inside your orchestration
```{note} ```{note}
The Username & Password, and API settings only work with the Generic Extractor. Other modules (like the screenshot enricher) can only use the `cookies` options. Furthermore, many sites can still detect bots and block username/password logins. Twitter/X and YouTube are two prominent ones that block username/password logging. Currently, the Username & Password, and API settings only work with the Generic and Antibot Extractors. Furthermore, many sites can still detect bots and block username/password logins. Twitter/X and YouTube are two prominent ones that block username/password logging.
One of the 'Cookies' options is recommended for the most robust archiving, but it still isn't guaranteed to work. One of the 'Cookies' options is recommended for the most robust archiving, but it still isn't guaranteed to work.
``` ```