mirror of
https://github.com/goauthentik/authentik.git
synced 2026-06-17 19:09:11 +03:00
core, web: update translations (#23018)
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: authentik-automation[bot] <135050075+authentik-automation[bot]@users.noreply.github.com>
This commit is contained in:
authentik-automation[bot]
committed by
GitHub
GitHub
parent
1d61e6b4de
commit
959ba246a8
@@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2026-06-11 00:42+0000\n"
|
||||
"POT-Creation-Date: 2026-06-15 00:41+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@@ -4013,6 +4013,14 @@ msgid ""
|
||||
"Background task to import FIDO Alliance MDS blob and AAGUIDs into database."
|
||||
msgstr ""
|
||||
|
||||
#: authentik/stages/captcha/models.py
|
||||
msgid "Form encoded"
|
||||
msgstr ""
|
||||
|
||||
#: authentik/stages/captcha/models.py
|
||||
msgid "JSON"
|
||||
msgstr ""
|
||||
|
||||
#: authentik/stages/captcha/models.py
|
||||
msgid "Public key, acquired your captcha Provider."
|
||||
msgstr ""
|
||||
|
||||
Binary file not shown.
Binary file not shown.
Binary file not shown.
+44
-1
@@ -9311,7 +9311,7 @@ Vazby na skupiny/uživatele jsou kontrolovány vůči uživateli události.</tar
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link">
|
||||
<source>API keys can be obtained from the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<note from="lit-localize">Supplementary help text with link to provider dashboard.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="s87f858ca3c8e5579">
|
||||
@@ -11233,6 +11233,49 @@ Vazby na skupiny/uživatele jsou kontrolovány vůči uživateli události.</tar
|
||||
<trans-unit id="sd1b98c71ea0d603b">
|
||||
<source>Flags allow you to enable new functionality and behavior in authentik early.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s00640d26256c4878">
|
||||
<source>Cap Endpoint</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s40bf0fb50dad7090">
|
||||
<source>https://cap.example.com/site-key/</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sc18a73a5831aca7b">
|
||||
<source>For Cap, prefer the self-hosted widget asset, for example https://cap.example.com/assets/widget.js. If using a CDN, pin a reviewed release.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s4e1e8db555003a9a">
|
||||
<source>Cap's server-side verification endpoint, for example https://cap.example.com/site-key/siteverify.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sdb752cddc543357d">
|
||||
<source>Request Content Type</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s8afdb5c5a27d37eb">
|
||||
<source>Content-Type used for server-side verification. Cap requires JSON; most other providers use form-encoded requests.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.form">
|
||||
<source>Form encoded</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.json">
|
||||
<source>JSON</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap">
|
||||
<source>Cap</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.description">
|
||||
<source>Cap is a self-hostable CAPTCHA server that uses proof-of-work challenges.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.setup-guide">
|
||||
<source>Cap documentation</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.cap-endpoint.description">
|
||||
<source>The public site-key endpoint of your Cap server.</source>
|
||||
<note from="lit-localize">Description for Cap endpoint field.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link.cap">
|
||||
<source>Use the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >`}"/>
|
||||
to self-host Cap and configure the endpoint.</source>
|
||||
<note from="lit-localize">Supplementary help text with link to Cap documentation.</note>
|
||||
</trans-unit>
|
||||
</body>
|
||||
</file>
|
||||
</xliff>
|
||||
|
||||
+44
-1
@@ -9343,7 +9343,7 @@ Bindings zu Gruppen/Benutzern werden mit dem Benutzer des Ereignisses abgegliche
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link">
|
||||
<source>API keys can be obtained from the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<note from="lit-localize">Supplementary help text with link to provider dashboard.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="s87f858ca3c8e5579">
|
||||
@@ -11265,6 +11265,49 @@ Bindings zu Gruppen/Benutzern werden mit dem Benutzer des Ereignisses abgegliche
|
||||
<trans-unit id="sd1b98c71ea0d603b">
|
||||
<source>Flags allow you to enable new functionality and behavior in authentik early.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s00640d26256c4878">
|
||||
<source>Cap Endpoint</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s40bf0fb50dad7090">
|
||||
<source>https://cap.example.com/site-key/</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sc18a73a5831aca7b">
|
||||
<source>For Cap, prefer the self-hosted widget asset, for example https://cap.example.com/assets/widget.js. If using a CDN, pin a reviewed release.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s4e1e8db555003a9a">
|
||||
<source>Cap's server-side verification endpoint, for example https://cap.example.com/site-key/siteverify.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sdb752cddc543357d">
|
||||
<source>Request Content Type</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s8afdb5c5a27d37eb">
|
||||
<source>Content-Type used for server-side verification. Cap requires JSON; most other providers use form-encoded requests.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.form">
|
||||
<source>Form encoded</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.json">
|
||||
<source>JSON</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap">
|
||||
<source>Cap</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.description">
|
||||
<source>Cap is a self-hostable CAPTCHA server that uses proof-of-work challenges.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.setup-guide">
|
||||
<source>Cap documentation</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.cap-endpoint.description">
|
||||
<source>The public site-key endpoint of your Cap server.</source>
|
||||
<note from="lit-localize">Description for Cap endpoint field.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link.cap">
|
||||
<source>Use the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >`}"/>
|
||||
to self-host Cap and configure the endpoint.</source>
|
||||
<note from="lit-localize">Supplementary help text with link to Cap documentation.</note>
|
||||
</trans-unit>
|
||||
</body>
|
||||
</file>
|
||||
</xliff>
|
||||
|
||||
+44
-1
@@ -7335,7 +7335,7 @@ Bindings to groups/users are checked against the user of the event.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link">
|
||||
<source>API keys can be obtained from the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<note from="lit-localize">Supplementary help text with link to provider dashboard.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="s87f858ca3c8e5579">
|
||||
@@ -9257,6 +9257,49 @@ Bindings to groups/users are checked against the user of the event.</source>
|
||||
<trans-unit id="sd1b98c71ea0d603b">
|
||||
<source>Flags allow you to enable new functionality and behavior in authentik early.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s00640d26256c4878">
|
||||
<source>Cap Endpoint</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s40bf0fb50dad7090">
|
||||
<source>https://cap.example.com/site-key/</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sc18a73a5831aca7b">
|
||||
<source>For Cap, prefer the self-hosted widget asset, for example https://cap.example.com/assets/widget.js. If using a CDN, pin a reviewed release.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s4e1e8db555003a9a">
|
||||
<source>Cap's server-side verification endpoint, for example https://cap.example.com/site-key/siteverify.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sdb752cddc543357d">
|
||||
<source>Request Content Type</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s8afdb5c5a27d37eb">
|
||||
<source>Content-Type used for server-side verification. Cap requires JSON; most other providers use form-encoded requests.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.form">
|
||||
<source>Form encoded</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.json">
|
||||
<source>JSON</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap">
|
||||
<source>Cap</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.description">
|
||||
<source>Cap is a self-hostable CAPTCHA server that uses proof-of-work challenges.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.setup-guide">
|
||||
<source>Cap documentation</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.cap-endpoint.description">
|
||||
<source>The public site-key endpoint of your Cap server.</source>
|
||||
<note from="lit-localize">Description for Cap endpoint field.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link.cap">
|
||||
<source>Use the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >`}"/>
|
||||
to self-host Cap and configure the endpoint.</source>
|
||||
<note from="lit-localize">Supplementary help text with link to Cap documentation.</note>
|
||||
</trans-unit>
|
||||
</body>
|
||||
</file>
|
||||
</xliff>
|
||||
|
||||
+44
-1
@@ -9270,7 +9270,7 @@ Las vinculaciones a grupos/usuarios se verifican en función del usuario del eve
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link">
|
||||
<source>API keys can be obtained from the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<note from="lit-localize">Supplementary help text with link to provider dashboard.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="s87f858ca3c8e5579">
|
||||
@@ -11192,6 +11192,49 @@ Las vinculaciones a grupos/usuarios se verifican en función del usuario del eve
|
||||
<trans-unit id="sd1b98c71ea0d603b">
|
||||
<source>Flags allow you to enable new functionality and behavior in authentik early.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s00640d26256c4878">
|
||||
<source>Cap Endpoint</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s40bf0fb50dad7090">
|
||||
<source>https://cap.example.com/site-key/</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sc18a73a5831aca7b">
|
||||
<source>For Cap, prefer the self-hosted widget asset, for example https://cap.example.com/assets/widget.js. If using a CDN, pin a reviewed release.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s4e1e8db555003a9a">
|
||||
<source>Cap's server-side verification endpoint, for example https://cap.example.com/site-key/siteverify.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sdb752cddc543357d">
|
||||
<source>Request Content Type</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s8afdb5c5a27d37eb">
|
||||
<source>Content-Type used for server-side verification. Cap requires JSON; most other providers use form-encoded requests.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.form">
|
||||
<source>Form encoded</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.json">
|
||||
<source>JSON</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap">
|
||||
<source>Cap</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.description">
|
||||
<source>Cap is a self-hostable CAPTCHA server that uses proof-of-work challenges.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.setup-guide">
|
||||
<source>Cap documentation</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.cap-endpoint.description">
|
||||
<source>The public site-key endpoint of your Cap server.</source>
|
||||
<note from="lit-localize">Description for Cap endpoint field.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link.cap">
|
||||
<source>Use the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >`}"/>
|
||||
to self-host Cap and configure the endpoint.</source>
|
||||
<note from="lit-localize">Supplementary help text with link to Cap documentation.</note>
|
||||
</trans-unit>
|
||||
</body>
|
||||
</file>
|
||||
</xliff>
|
||||
|
||||
+44
-1
@@ -9509,7 +9509,7 @@ Liitokset käyttäjiin/ryhmiin tarkistetaan tapahtuman käyttäjästä.</target>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link">
|
||||
<source>API keys can be obtained from the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<note from="lit-localize">Supplementary help text with link to provider dashboard.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="s87f858ca3c8e5579">
|
||||
@@ -11431,6 +11431,49 @@ Liitokset käyttäjiin/ryhmiin tarkistetaan tapahtuman käyttäjästä.</target>
|
||||
<trans-unit id="sd1b98c71ea0d603b">
|
||||
<source>Flags allow you to enable new functionality and behavior in authentik early.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s00640d26256c4878">
|
||||
<source>Cap Endpoint</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s40bf0fb50dad7090">
|
||||
<source>https://cap.example.com/site-key/</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sc18a73a5831aca7b">
|
||||
<source>For Cap, prefer the self-hosted widget asset, for example https://cap.example.com/assets/widget.js. If using a CDN, pin a reviewed release.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s4e1e8db555003a9a">
|
||||
<source>Cap's server-side verification endpoint, for example https://cap.example.com/site-key/siteverify.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sdb752cddc543357d">
|
||||
<source>Request Content Type</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s8afdb5c5a27d37eb">
|
||||
<source>Content-Type used for server-side verification. Cap requires JSON; most other providers use form-encoded requests.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.form">
|
||||
<source>Form encoded</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.json">
|
||||
<source>JSON</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap">
|
||||
<source>Cap</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.description">
|
||||
<source>Cap is a self-hostable CAPTCHA server that uses proof-of-work challenges.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.setup-guide">
|
||||
<source>Cap documentation</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.cap-endpoint.description">
|
||||
<source>The public site-key endpoint of your Cap server.</source>
|
||||
<note from="lit-localize">Description for Cap endpoint field.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link.cap">
|
||||
<source>Use the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >`}"/>
|
||||
to self-host Cap and configure the endpoint.</source>
|
||||
<note from="lit-localize">Supplementary help text with link to Cap documentation.</note>
|
||||
</trans-unit>
|
||||
</body>
|
||||
</file>
|
||||
</xliff>
|
||||
|
||||
+44
-1
@@ -9498,7 +9498,7 @@ Les liaisons avec les groupes/utilisateurs sont vérifiées par rapport à l'uti
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link">
|
||||
<source>API keys can be obtained from the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<note from="lit-localize">Supplementary help text with link to provider dashboard.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="s87f858ca3c8e5579">
|
||||
@@ -11420,6 +11420,49 @@ Les liaisons avec les groupes/utilisateurs sont vérifiées par rapport à l'uti
|
||||
<trans-unit id="sd1b98c71ea0d603b">
|
||||
<source>Flags allow you to enable new functionality and behavior in authentik early.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s00640d26256c4878">
|
||||
<source>Cap Endpoint</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s40bf0fb50dad7090">
|
||||
<source>https://cap.example.com/site-key/</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sc18a73a5831aca7b">
|
||||
<source>For Cap, prefer the self-hosted widget asset, for example https://cap.example.com/assets/widget.js. If using a CDN, pin a reviewed release.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s4e1e8db555003a9a">
|
||||
<source>Cap's server-side verification endpoint, for example https://cap.example.com/site-key/siteverify.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sdb752cddc543357d">
|
||||
<source>Request Content Type</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s8afdb5c5a27d37eb">
|
||||
<source>Content-Type used for server-side verification. Cap requires JSON; most other providers use form-encoded requests.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.form">
|
||||
<source>Form encoded</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.json">
|
||||
<source>JSON</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap">
|
||||
<source>Cap</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.description">
|
||||
<source>Cap is a self-hostable CAPTCHA server that uses proof-of-work challenges.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.setup-guide">
|
||||
<source>Cap documentation</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.cap-endpoint.description">
|
||||
<source>The public site-key endpoint of your Cap server.</source>
|
||||
<note from="lit-localize">Description for Cap endpoint field.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link.cap">
|
||||
<source>Use the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >`}"/>
|
||||
to self-host Cap and configure the endpoint.</source>
|
||||
<note from="lit-localize">Supplementary help text with link to Cap documentation.</note>
|
||||
</trans-unit>
|
||||
</body>
|
||||
</file>
|
||||
</xliff>
|
||||
|
||||
+44
-1
@@ -9219,7 +9219,7 @@ Bindings to groups/users are checked against the user of the event.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link">
|
||||
<source>API keys can be obtained from the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<note from="lit-localize">Supplementary help text with link to provider dashboard.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="s87f858ca3c8e5579">
|
||||
@@ -11141,6 +11141,49 @@ Bindings to groups/users are checked against the user of the event.</source>
|
||||
<trans-unit id="sd1b98c71ea0d603b">
|
||||
<source>Flags allow you to enable new functionality and behavior in authentik early.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s00640d26256c4878">
|
||||
<source>Cap Endpoint</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s40bf0fb50dad7090">
|
||||
<source>https://cap.example.com/site-key/</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sc18a73a5831aca7b">
|
||||
<source>For Cap, prefer the self-hosted widget asset, for example https://cap.example.com/assets/widget.js. If using a CDN, pin a reviewed release.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s4e1e8db555003a9a">
|
||||
<source>Cap's server-side verification endpoint, for example https://cap.example.com/site-key/siteverify.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sdb752cddc543357d">
|
||||
<source>Request Content Type</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s8afdb5c5a27d37eb">
|
||||
<source>Content-Type used for server-side verification. Cap requires JSON; most other providers use form-encoded requests.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.form">
|
||||
<source>Form encoded</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.json">
|
||||
<source>JSON</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap">
|
||||
<source>Cap</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.description">
|
||||
<source>Cap is a self-hostable CAPTCHA server that uses proof-of-work challenges.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.setup-guide">
|
||||
<source>Cap documentation</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.cap-endpoint.description">
|
||||
<source>The public site-key endpoint of your Cap server.</source>
|
||||
<note from="lit-localize">Description for Cap endpoint field.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link.cap">
|
||||
<source>Use the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >`}"/>
|
||||
to self-host Cap and configure the endpoint.</source>
|
||||
<note from="lit-localize">Supplementary help text with link to Cap documentation.</note>
|
||||
</trans-unit>
|
||||
</body>
|
||||
</file>
|
||||
</xliff>
|
||||
|
||||
+44
-1
@@ -9499,7 +9499,7 @@ Bindings to groups/users are checked against the user of the event.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link">
|
||||
<source>API keys can be obtained from the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<note from="lit-localize">Supplementary help text with link to provider dashboard.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="s87f858ca3c8e5579">
|
||||
@@ -11421,6 +11421,49 @@ Bindings to groups/users are checked against the user of the event.</source>
|
||||
<trans-unit id="sd1b98c71ea0d603b">
|
||||
<source>Flags allow you to enable new functionality and behavior in authentik early.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s00640d26256c4878">
|
||||
<source>Cap Endpoint</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s40bf0fb50dad7090">
|
||||
<source>https://cap.example.com/site-key/</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sc18a73a5831aca7b">
|
||||
<source>For Cap, prefer the self-hosted widget asset, for example https://cap.example.com/assets/widget.js. If using a CDN, pin a reviewed release.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s4e1e8db555003a9a">
|
||||
<source>Cap's server-side verification endpoint, for example https://cap.example.com/site-key/siteverify.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sdb752cddc543357d">
|
||||
<source>Request Content Type</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s8afdb5c5a27d37eb">
|
||||
<source>Content-Type used for server-side verification. Cap requires JSON; most other providers use form-encoded requests.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.form">
|
||||
<source>Form encoded</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.json">
|
||||
<source>JSON</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap">
|
||||
<source>Cap</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.description">
|
||||
<source>Cap is a self-hostable CAPTCHA server that uses proof-of-work challenges.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.setup-guide">
|
||||
<source>Cap documentation</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.cap-endpoint.description">
|
||||
<source>The public site-key endpoint of your Cap server.</source>
|
||||
<note from="lit-localize">Description for Cap endpoint field.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link.cap">
|
||||
<source>Use the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >`}"/>
|
||||
to self-host Cap and configure the endpoint.</source>
|
||||
<note from="lit-localize">Supplementary help text with link to Cap documentation.</note>
|
||||
</trans-unit>
|
||||
</body>
|
||||
</file>
|
||||
</xliff>
|
||||
|
||||
+44
-1
@@ -8871,7 +8871,7 @@ Bindings to groups/users are checked against the user of the event.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link">
|
||||
<source>API keys can be obtained from the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<note from="lit-localize">Supplementary help text with link to provider dashboard.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="s87f858ca3c8e5579">
|
||||
@@ -10793,6 +10793,49 @@ Bindings to groups/users are checked against the user of the event.</source>
|
||||
<trans-unit id="sd1b98c71ea0d603b">
|
||||
<source>Flags allow you to enable new functionality and behavior in authentik early.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s00640d26256c4878">
|
||||
<source>Cap Endpoint</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s40bf0fb50dad7090">
|
||||
<source>https://cap.example.com/site-key/</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sc18a73a5831aca7b">
|
||||
<source>For Cap, prefer the self-hosted widget asset, for example https://cap.example.com/assets/widget.js. If using a CDN, pin a reviewed release.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s4e1e8db555003a9a">
|
||||
<source>Cap's server-side verification endpoint, for example https://cap.example.com/site-key/siteverify.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sdb752cddc543357d">
|
||||
<source>Request Content Type</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s8afdb5c5a27d37eb">
|
||||
<source>Content-Type used for server-side verification. Cap requires JSON; most other providers use form-encoded requests.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.form">
|
||||
<source>Form encoded</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.json">
|
||||
<source>JSON</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap">
|
||||
<source>Cap</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.description">
|
||||
<source>Cap is a self-hostable CAPTCHA server that uses proof-of-work challenges.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.setup-guide">
|
||||
<source>Cap documentation</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.cap-endpoint.description">
|
||||
<source>The public site-key endpoint of your Cap server.</source>
|
||||
<note from="lit-localize">Description for Cap endpoint field.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link.cap">
|
||||
<source>Use the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >`}"/>
|
||||
to self-host Cap and configure the endpoint.</source>
|
||||
<note from="lit-localize">Supplementary help text with link to Cap documentation.</note>
|
||||
</trans-unit>
|
||||
</body>
|
||||
</file>
|
||||
</xliff>
|
||||
|
||||
+44
-1
@@ -8557,7 +8557,7 @@ Bindingen naar groepen/gebruikers worden gecontroleerd tegen de gebruiker van de
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link">
|
||||
<source>API keys can be obtained from the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<note from="lit-localize">Supplementary help text with link to provider dashboard.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="s87f858ca3c8e5579">
|
||||
@@ -10479,6 +10479,49 @@ Bindingen naar groepen/gebruikers worden gecontroleerd tegen de gebruiker van de
|
||||
<trans-unit id="sd1b98c71ea0d603b">
|
||||
<source>Flags allow you to enable new functionality and behavior in authentik early.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s00640d26256c4878">
|
||||
<source>Cap Endpoint</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s40bf0fb50dad7090">
|
||||
<source>https://cap.example.com/site-key/</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sc18a73a5831aca7b">
|
||||
<source>For Cap, prefer the self-hosted widget asset, for example https://cap.example.com/assets/widget.js. If using a CDN, pin a reviewed release.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s4e1e8db555003a9a">
|
||||
<source>Cap's server-side verification endpoint, for example https://cap.example.com/site-key/siteverify.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sdb752cddc543357d">
|
||||
<source>Request Content Type</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s8afdb5c5a27d37eb">
|
||||
<source>Content-Type used for server-side verification. Cap requires JSON; most other providers use form-encoded requests.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.form">
|
||||
<source>Form encoded</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.json">
|
||||
<source>JSON</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap">
|
||||
<source>Cap</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.description">
|
||||
<source>Cap is a self-hostable CAPTCHA server that uses proof-of-work challenges.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.setup-guide">
|
||||
<source>Cap documentation</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.cap-endpoint.description">
|
||||
<source>The public site-key endpoint of your Cap server.</source>
|
||||
<note from="lit-localize">Description for Cap endpoint field.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link.cap">
|
||||
<source>Use the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >`}"/>
|
||||
to self-host Cap and configure the endpoint.</source>
|
||||
<note from="lit-localize">Supplementary help text with link to Cap documentation.</note>
|
||||
</trans-unit>
|
||||
</body>
|
||||
</file>
|
||||
</xliff>
|
||||
|
||||
+44
-1
@@ -8895,7 +8895,7 @@ Powiązania z grupami/użytkownikami są sprawdzane względem użytkownika zdarz
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link">
|
||||
<source>API keys can be obtained from the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<note from="lit-localize">Supplementary help text with link to provider dashboard.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="s87f858ca3c8e5579">
|
||||
@@ -10817,6 +10817,49 @@ Powiązania z grupami/użytkownikami są sprawdzane względem użytkownika zdarz
|
||||
<trans-unit id="sd1b98c71ea0d603b">
|
||||
<source>Flags allow you to enable new functionality and behavior in authentik early.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s00640d26256c4878">
|
||||
<source>Cap Endpoint</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s40bf0fb50dad7090">
|
||||
<source>https://cap.example.com/site-key/</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sc18a73a5831aca7b">
|
||||
<source>For Cap, prefer the self-hosted widget asset, for example https://cap.example.com/assets/widget.js. If using a CDN, pin a reviewed release.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s4e1e8db555003a9a">
|
||||
<source>Cap's server-side verification endpoint, for example https://cap.example.com/site-key/siteverify.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sdb752cddc543357d">
|
||||
<source>Request Content Type</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s8afdb5c5a27d37eb">
|
||||
<source>Content-Type used for server-side verification. Cap requires JSON; most other providers use form-encoded requests.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.form">
|
||||
<source>Form encoded</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.json">
|
||||
<source>JSON</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap">
|
||||
<source>Cap</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.description">
|
||||
<source>Cap is a self-hostable CAPTCHA server that uses proof-of-work challenges.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.setup-guide">
|
||||
<source>Cap documentation</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.cap-endpoint.description">
|
||||
<source>The public site-key endpoint of your Cap server.</source>
|
||||
<note from="lit-localize">Description for Cap endpoint field.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link.cap">
|
||||
<source>Use the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >`}"/>
|
||||
to self-host Cap and configure the endpoint.</source>
|
||||
<note from="lit-localize">Supplementary help text with link to Cap documentation.</note>
|
||||
</trans-unit>
|
||||
</body>
|
||||
</file>
|
||||
</xliff>
|
||||
|
||||
+44
-1
@@ -9491,7 +9491,7 @@ por exemplo: <x id="0" equiv-text="<code>"/>oci://registry.domain.tld/path
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link">
|
||||
<source>API keys can be obtained from the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<note from="lit-localize">Supplementary help text with link to provider dashboard.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="s87f858ca3c8e5579">
|
||||
@@ -11413,6 +11413,49 @@ por exemplo: <x id="0" equiv-text="<code>"/>oci://registry.domain.tld/path
|
||||
<trans-unit id="sd1b98c71ea0d603b">
|
||||
<source>Flags allow you to enable new functionality and behavior in authentik early.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s00640d26256c4878">
|
||||
<source>Cap Endpoint</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s40bf0fb50dad7090">
|
||||
<source>https://cap.example.com/site-key/</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sc18a73a5831aca7b">
|
||||
<source>For Cap, prefer the self-hosted widget asset, for example https://cap.example.com/assets/widget.js. If using a CDN, pin a reviewed release.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s4e1e8db555003a9a">
|
||||
<source>Cap's server-side verification endpoint, for example https://cap.example.com/site-key/siteverify.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sdb752cddc543357d">
|
||||
<source>Request Content Type</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s8afdb5c5a27d37eb">
|
||||
<source>Content-Type used for server-side verification. Cap requires JSON; most other providers use form-encoded requests.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.form">
|
||||
<source>Form encoded</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.json">
|
||||
<source>JSON</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap">
|
||||
<source>Cap</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.description">
|
||||
<source>Cap is a self-hostable CAPTCHA server that uses proof-of-work challenges.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.setup-guide">
|
||||
<source>Cap documentation</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.cap-endpoint.description">
|
||||
<source>The public site-key endpoint of your Cap server.</source>
|
||||
<note from="lit-localize">Description for Cap endpoint field.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link.cap">
|
||||
<source>Use the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >`}"/>
|
||||
to self-host Cap and configure the endpoint.</source>
|
||||
<note from="lit-localize">Supplementary help text with link to Cap documentation.</note>
|
||||
</trans-unit>
|
||||
</body>
|
||||
</file>
|
||||
</xliff>
|
||||
|
||||
+44
-1
@@ -8981,7 +8981,7 @@ Bindings to groups/users are checked against the user of the event.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link">
|
||||
<source>API keys can be obtained from the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<note from="lit-localize">Supplementary help text with link to provider dashboard.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="s87f858ca3c8e5579">
|
||||
@@ -10903,6 +10903,49 @@ Bindings to groups/users are checked against the user of the event.</source>
|
||||
<trans-unit id="sd1b98c71ea0d603b">
|
||||
<source>Flags allow you to enable new functionality and behavior in authentik early.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s00640d26256c4878">
|
||||
<source>Cap Endpoint</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s40bf0fb50dad7090">
|
||||
<source>https://cap.example.com/site-key/</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sc18a73a5831aca7b">
|
||||
<source>For Cap, prefer the self-hosted widget asset, for example https://cap.example.com/assets/widget.js. If using a CDN, pin a reviewed release.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s4e1e8db555003a9a">
|
||||
<source>Cap's server-side verification endpoint, for example https://cap.example.com/site-key/siteverify.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sdb752cddc543357d">
|
||||
<source>Request Content Type</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s8afdb5c5a27d37eb">
|
||||
<source>Content-Type used for server-side verification. Cap requires JSON; most other providers use form-encoded requests.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.form">
|
||||
<source>Form encoded</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.json">
|
||||
<source>JSON</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap">
|
||||
<source>Cap</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.description">
|
||||
<source>Cap is a self-hostable CAPTCHA server that uses proof-of-work challenges.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.setup-guide">
|
||||
<source>Cap documentation</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.cap-endpoint.description">
|
||||
<source>The public site-key endpoint of your Cap server.</source>
|
||||
<note from="lit-localize">Description for Cap endpoint field.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link.cap">
|
||||
<source>Use the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >`}"/>
|
||||
to self-host Cap and configure the endpoint.</source>
|
||||
<note from="lit-localize">Supplementary help text with link to Cap documentation.</note>
|
||||
</trans-unit>
|
||||
</body>
|
||||
</file>
|
||||
</xliff>
|
||||
|
||||
+44
-1
@@ -8971,7 +8971,7 @@ Gruplara/kullanıcılara yapılan bağlamalar, etkinliğin kullanıcısına kar
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link">
|
||||
<source>API keys can be obtained from the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<note from="lit-localize">Supplementary help text with link to provider dashboard.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="s87f858ca3c8e5579">
|
||||
@@ -10893,6 +10893,49 @@ Gruplara/kullanıcılara yapılan bağlamalar, etkinliğin kullanıcısına kar
|
||||
<trans-unit id="sd1b98c71ea0d603b">
|
||||
<source>Flags allow you to enable new functionality and behavior in authentik early.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s00640d26256c4878">
|
||||
<source>Cap Endpoint</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s40bf0fb50dad7090">
|
||||
<source>https://cap.example.com/site-key/</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sc18a73a5831aca7b">
|
||||
<source>For Cap, prefer the self-hosted widget asset, for example https://cap.example.com/assets/widget.js. If using a CDN, pin a reviewed release.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s4e1e8db555003a9a">
|
||||
<source>Cap's server-side verification endpoint, for example https://cap.example.com/site-key/siteverify.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sdb752cddc543357d">
|
||||
<source>Request Content Type</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s8afdb5c5a27d37eb">
|
||||
<source>Content-Type used for server-side verification. Cap requires JSON; most other providers use form-encoded requests.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.form">
|
||||
<source>Form encoded</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.json">
|
||||
<source>JSON</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap">
|
||||
<source>Cap</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.description">
|
||||
<source>Cap is a self-hostable CAPTCHA server that uses proof-of-work challenges.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.setup-guide">
|
||||
<source>Cap documentation</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.cap-endpoint.description">
|
||||
<source>The public site-key endpoint of your Cap server.</source>
|
||||
<note from="lit-localize">Description for Cap endpoint field.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link.cap">
|
||||
<source>Use the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >`}"/>
|
||||
to self-host Cap and configure the endpoint.</source>
|
||||
<note from="lit-localize">Supplementary help text with link to Cap documentation.</note>
|
||||
</trans-unit>
|
||||
</body>
|
||||
</file>
|
||||
</xliff>
|
||||
|
||||
+44
-1
@@ -9756,7 +9756,7 @@ Bindings to groups/users are checked against the user of the event.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link">
|
||||
<source>API keys can be obtained from the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<note from="lit-localize">Supplementary help text with link to provider dashboard.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="s87f858ca3c8e5579">
|
||||
@@ -11711,6 +11711,49 @@ Bindings to groups/users are checked against the user of the event.</source>
|
||||
<trans-unit id="sd1b98c71ea0d603b">
|
||||
<source>Flags allow you to enable new functionality and behavior in authentik early.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s00640d26256c4878">
|
||||
<source>Cap Endpoint</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s40bf0fb50dad7090">
|
||||
<source>https://cap.example.com/site-key/</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sc18a73a5831aca7b">
|
||||
<source>For Cap, prefer the self-hosted widget asset, for example https://cap.example.com/assets/widget.js. If using a CDN, pin a reviewed release.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s4e1e8db555003a9a">
|
||||
<source>Cap's server-side verification endpoint, for example https://cap.example.com/site-key/siteverify.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sdb752cddc543357d">
|
||||
<source>Request Content Type</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s8afdb5c5a27d37eb">
|
||||
<source>Content-Type used for server-side verification. Cap requires JSON; most other providers use form-encoded requests.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.form">
|
||||
<source>Form encoded</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.json">
|
||||
<source>JSON</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap">
|
||||
<source>Cap</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.description">
|
||||
<source>Cap is a self-hostable CAPTCHA server that uses proof-of-work challenges.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.setup-guide">
|
||||
<source>Cap documentation</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.cap-endpoint.description">
|
||||
<source>The public site-key endpoint of your Cap server.</source>
|
||||
<note from="lit-localize">Description for Cap endpoint field.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link.cap">
|
||||
<source>Use the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >`}"/>
|
||||
to self-host Cap and configure the endpoint.</source>
|
||||
<note from="lit-localize">Supplementary help text with link to Cap documentation.</note>
|
||||
</trans-unit>
|
||||
</body>
|
||||
</file>
|
||||
</xliff>
|
||||
|
||||
+44
-1
@@ -8609,7 +8609,7 @@ Bindings to groups/users are checked against the user of the event.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link">
|
||||
<source>API keys can be obtained from the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >.`}"/></source>
|
||||
<note from="lit-localize">Supplementary help text with link to provider dashboard.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="s87f858ca3c8e5579">
|
||||
@@ -10531,6 +10531,49 @@ Bindings to groups/users are checked against the user of the event.</source>
|
||||
<trans-unit id="sd1b98c71ea0d603b">
|
||||
<source>Flags allow you to enable new functionality and behavior in authentik early.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s00640d26256c4878">
|
||||
<source>Cap Endpoint</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s40bf0fb50dad7090">
|
||||
<source>https://cap.example.com/site-key/</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sc18a73a5831aca7b">
|
||||
<source>For Cap, prefer the self-hosted widget asset, for example https://cap.example.com/assets/widget.js. If using a CDN, pin a reviewed release.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s4e1e8db555003a9a">
|
||||
<source>Cap's server-side verification endpoint, for example https://cap.example.com/site-key/siteverify.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="sdb752cddc543357d">
|
||||
<source>Request Content Type</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="s8afdb5c5a27d37eb">
|
||||
<source>Content-Type used for server-side verification. Cap requires JSON; most other providers use form-encoded requests.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.form">
|
||||
<source>Form encoded</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.request-content-type.json">
|
||||
<source>JSON</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap">
|
||||
<source>Cap</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.description">
|
||||
<source>Cap is a self-hostable CAPTCHA server that uses proof-of-work challenges.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.providers.cap.setup-guide">
|
||||
<source>Cap documentation</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.cap-endpoint.description">
|
||||
<source>The public site-key endpoint of your Cap server.</source>
|
||||
<note from="lit-localize">Description for Cap endpoint field.</note>
|
||||
</trans-unit>
|
||||
<trans-unit id="captcha.provider-link.cap">
|
||||
<source>Use the
|
||||
<x id="0" equiv-text="${html `<a target="_blank" rel="noopener noreferrer" href=${keyURL} >${formatAPISource()}</a >`}"/>
|
||||
to self-host Cap and configure the endpoint.</source>
|
||||
<note from="lit-localize">Supplementary help text with link to Cap documentation.</note>
|
||||
</trans-unit>
|
||||
</body>
|
||||
</file>
|
||||
</xliff>
|
||||
|
||||
Reference in New Issue
Block a user