Laravel 3rd-party Integrations: Secure Live API Keys

There's a trick how you can check if "live" keys aren't accidentally used on someone's local computer, or in a staging/testing environment. Let me show you.

- - - - -
Support the channel by checking out my products:

- - - - -
Other places to follow:

[phoenixedge]

Can’t recommend Stephen enough. He’s helped our Laravel app stand up to scrutiny of security audits. He’s the only Laravel focused resource we could find who does this.

[JouvaMoufette]

This is where things such as CI/CD come in handy as well. You use a template to build the config files for production, and have the CI/CD tools replace the relevant parts of the template with the correct keys, then the only thing that needs those keys is your CI/CD software.

[DunckingTest]

im a junior full stack dev
i really enjoy your content ❤️

[davidadewale]

Thanks for the everyday updates on Laravel. However, I will like you to do a tutorial on how to integrate JWT Authorization with Laravel and social media login auth with Laravel.

Thanks 👍👌

[jamesbhatta]

Would love to see a video on how to store the keys on database the right way.

[pesheenmstafa]

This comment is not related to the topic but
I am wondering if we use Laravel sanctum with Laravel fortify

Does I have to override the logic of the registration and login

Because simply when I login with the default the fortify does not generate any record for
Logged in user
In table personal-access-token

Am I mistaken or to do that I have to overrides the default or with fortify is different approach or it depend on the type of the application

Dear povilas can you make a tutorial about that

[ivan_adamovich]

Good afternoon, sir
Could you describe how you, would solve a this problem or maybe this is a good topic for a lesson?

Let's say you're on a product page and you have to log in for adding page in bookmarks. You would expect to be redirected back to the product page, not to the homepage after login.

By default, Laravel redirects users to the home route after they login or create a new account (except when triggered auth middleware). But sometimes it makes sense to redirect them back to the page they were on before. 

Auth middleware works fine, but in the case of, for example, Livewire, it won't work because you can't apply middleware inside the Livewire component.

[ramus]

anyone can help me with laravel problem, which one is better? especially for performance on large table
or is it same? im confused

Query 1 = Topic::from('topic')->join( 'subject', 'subject.id', '=', 'topic.subject_id')->get()
vs
Query 2 = DB::table('topic')->join( 'subject', 'subject.id', '=', 'topic.subject_id')->get()

[Laflamablanca]

Lmao this is only really relevant to stripe or other service that have different style prod and dev keys. Really isn’t an issue at all. Your local env and prod env should not be exact copies…