forked from docs/internal-documentation
Gode, Sebastian
347265ea12
Reviewed-by: tischrei <tino.schreiber@t-systems.com> Co-authored-by: Gode, Sebastian <sebastian.gode@t-systems.com> Co-committed-by: Gode, Sebastian <sebastian.gode@t-systems.com>
20 lines
950 B
ReStructuredText
20 lines
950 B
ReStructuredText
=====================================
|
|
Getting Access to the Captcha Service
|
|
=====================================
|
|
|
|
.. note::
|
|
Due to a current issue with mCaptcha we can't provide unqiue accounts yet and will instead provide only the required keys for setting up your captcha solution.
|
|
|
|
If you need a captcha solution for one of your webpages please contact the Ecosystem Squad by writing an E-Mail to: `DL OTC Ecosystem Squad <mailto:otc_ecosystem_squad@t-systems.com>`
|
|
Please state the following:
|
|
|
|
1. Your application name
|
|
|
|
.. tip::
|
|
For example a contact formular can take ~5s for a client to solve to prevent a lot of spam, while just checking before redirecting to a webpage should be done in less than 1s.
|
|
|
|
2. Desired Average Solving time.
|
|
|
|
We will provide you with a public sitekey which you will need to integrate the captcha access as well as a secret key which your backend needs for verifying whether the captcha was solved or not.
|
|
|