overwrite passport keys creation location?

Why do you want to do this?

I had a look at the source code and the Passport class has a public keyPath property that is used to determine where to store the keys. However I dont see how you would go setting the path

There is a way to load thd keys from another location so might need to manually move the keys

Passport::loadKeysFrom('/var/http/path/to/files');

These tests might help

https://github.com/laravel/passport/blob/6cae8eba19e8fa817b337bc86970f7fb59ec5787/tests/KeysCommandTest.php

To be honest I would leave as is unless you have a deal breaker reason to change

@d9705996 thanks for looking into this.

We are using passport with Password Grant Client which generate jwt tokens to auth in our JSON API.

I have some doubt about the SSL keys for Passport the command generated with the command artisan passport:keys or artisan passport:install I am not pretty sure how to deal with it in our deployment process for staging or production..

I could stored the keys in the deployment scripts and always generate the files (./storage/oauth-private.key, ./storage/oauth-public.key) with the same keys in each deployment process or run artisan passport:keys in each deployment process which will generate a new key for each deployment.

There is any security recommendation for this?

I guess that if a new pair key are generated for each deployment, the actual logged users jwt keys will be invalidad and they will need to logging again?