2022-11-14 17:13:24 +01:00
|
|
|
<?php
|
|
|
|
|
|
|
|
return [
|
|
|
|
|
2023-08-24 09:50:41 +02:00
|
|
|
'user_verification' => envUnlessEmpty('WEBAUTHN_USER_VERIFICATION', 'preferred'),
|
2022-12-09 10:52:17 +01:00
|
|
|
|
2022-11-14 17:13:24 +01:00
|
|
|
/*
|
|
|
|
|--------------------------------------------------------------------------
|
|
|
|
| Relaying Party
|
|
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
| We will use your application information to inform the device who is the
|
|
|
|
| relying party. While only the name is enough, you can further set
|
|
|
|
| a custom domain as ID and even an icon image data encoded as BASE64.
|
|
|
|
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
'relying_party' => [
|
2024-06-12 08:34:20 +02:00
|
|
|
'name' => envUnlessEmpty('WEBAUTHN_NAME', envUnlessEmpty('APP_NAME', '2FAuth')),
|
2023-08-24 09:50:41 +02:00
|
|
|
'id' => envUnlessEmpty('WEBAUTHN_ID', null),
|
2022-11-14 17:13:24 +01:00
|
|
|
],
|
|
|
|
|
|
|
|
/*
|
|
|
|
|--------------------------------------------------------------------------
|
|
|
|
| Challenge configuration
|
|
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
| When making challenges your application needs to push at least 16 bytes
|
|
|
|
| of randomness. Since we need to later check them, we'll also store the
|
|
|
|
| bytes for a small amount of time inside this current request session.
|
|
|
|
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
'challenge' => [
|
|
|
|
'bytes' => 16,
|
|
|
|
'timeout' => 60,
|
|
|
|
'key' => '_webauthn',
|
|
|
|
],
|
|
|
|
];
|