ONE_PILOT_PRIVATE_KEY can be any random alphanumeric string. If you are not sure what key to use, go to 1Pilot dashboard and open the page to add a new site: a random key will be generated for you, and you can copy / paste it in your file. Of course you are free to create a totally different key, just make sure you have the same key in your .env and on the 1Pilot dashboard.
ONE_PILOT_MAIL_FROM_ADDRESS email address that you use for send mail from your application. It's used by the email verification tool for ensure emails are properly send by your application.
3. add to your config/routes.yaml the following configuration:
ONE_PILOT_PRIVATE_KEY can be any random alphanumeric string. If you are not sure what key to use, go to 1Pilot dashboard and open the page to add a new site: a random key will be generated for you, and you can copy / paste it in your file. Of course you are free to create a totally different key, just make sure you have the same key in your .env and on the 1Pilot dashboard.
ONE_PILOT_MAIL_FROM_ADDRESS email address that you use for send mail from your application. It's used by the email verification tool for ensure emails are properly send by your application.
3. add to your config/routes.yaml the following configuration:
ONE_PILOT_PRIVATE_KEY can be any random alphanumeric string. If you are not sure what key to use, go to 1Pilot dashboard and open the page to add a new site: a random key will be generated for you, and you can copy / paste it in your file. Of course you are free to create a totally different key, just make sure you have the same key in your .env and on the 1Pilot dashboard.
ONE_PILOT_MAIL_FROM_ADDRESS email address that you use for send mail from your application. It's used by the email verification tool for ensure emails are properly send by your application.
3. add to your config/routes.yaml the following configuration:
one_pilot_private_key can be any random alphanumeric string. If you are not sure what key to use, go to 1Pilot dashboard and open the page to add a new site: a random key will be generated for you, and you can copy / paste it in your file. Of course you are free to create a totally different key, just make sure you have the same key in your parameters.yml and on the 1Pilot dashboard.
one_pilot_mail_from_address email address that you use for send mail from your application. It's used by the email verification tool for ensure emails are properly send by your application.
4. add to your app/config/routing.yml the following configuration:
5. add to your app/AppKernel.php file, in the registerBundles method, the following line:
1
...
2
new OnePilot\ClientBundle\OnePilotClientBundle(),
3
...
Copied!
Connection troubleshooting
Symfony firewall
A common issue with Symfony application is the Symfony firewall that doesn't allow 1Pilot servers to connect to your website and redirect requests they performs to /onepilot/* to the login form.
For fix that you have to allow anonymous access to /onepilot/ routes in the Symfony firewall and access_control list.
To proceed edit config/packages/security.yaml and add following lines in the firewalls section before the main entry:
1
1pilot:
2
pattern: ^/onepilot/
3
anonymous: true
Copied!
and the following line in the access_control section
If your server is not at time you can have issue to connect your application to 1Pilot. For solve that edit app/config/config.ymland add skip_timestamp_validation like bellow.
1
one_pilot_client:
2
private_key: "..."
3
skip_timestamp_validation: true
Copied!
Please note that this option will decrease security and that you should as much as possible set your server at the correct time.