Thank you for the help… Chatgpt could not do it actually what you have done. Just a request, you can now update the code as per latest development in FastAPI and update the okta token validation process as well. I have a question, can we use api routes, instead of the objectId when customizing openapi
Thank you for your comment and your suggestions 🚀🚀! I'm currently working on new tutorials about auth/authz with the latest version of FastAPI and I'll show how to do this with dependency injection, integrations with auth0, okta, and more! How are you planning to customise openapi with the API routes?
Thank you for the nice feedback! IP information is always available in the request headers. Whether you can get hold of the private IP depends on the client's network configuration and your own infrastructure. It's normally available, but which header to use depends a bit on your specific set up. I run some services in AWS with CloudFront and in that case I find all the information I need under the "X-Forwarded-For" header. I hope this helps!
Hi Luis thanks for the question! To generate a token after login you'd simply need to include the generate_jwt() function in your authentication server. You can implement the OAuth 2.0 flows, so the user would first log in and then request the access token using one of the flows, or you can issue the token right after the user successfully logs in (less recommended but practical in simple cases). To send the token, you respond with a 200 response, and in the response you include a payload with the JWT token. You may also want to include a refresh token and an ID token. So the response payload contains the following elements: {"access_token": "ey...", "id_token": "ey...", "refresh_token": "ey..."}. This is a standard response from an authorization server.
@microapis: Before we get it started I would like to ask you to subscribe also @microapis to a random person in the street: Before we know each other I would like you to make me a sandwich
If you liked the video, please give it a thumbs up and subscribe!
Will be nice to have a Keycloak+FastAPI tutorial, there aren't many
Thank you for the suggestion Guilherme - that's a very interesting idea! I'm adding it to the list of future videos 🚀!
Thank you for the help… Chatgpt could not do it actually what you have done. Just a request, you can now update the code as per latest development in FastAPI and update the okta token validation process as well.
I have a question, can we use api routes, instead of the objectId when customizing openapi
Thank you for your comment and your suggestions 🚀🚀! I'm currently working on new tutorials about auth/authz with the latest version of FastAPI and I'll show how to do this with dependency injection, integrations with auth0, okta, and more!
How are you planning to customise openapi with the API routes?
Excellent!
Thanks for the videos I have a question how i can get the private ip from the client inside the request.. it is possible?
Thank you for the nice feedback! IP information is always available in the request headers. Whether you can get hold of the private IP depends on the client's network configuration and your own infrastructure. It's normally available, but which header to use depends a bit on your specific set up. I run some services in AWS with CloudFront and in that case I find all the information I need under the "X-Forwarded-For" header. I hope this helps!
How to generate de jwt token from api without terminal like a login process with user and password?
Hi Luis thanks for the question! To generate a token after login you'd simply need to include the generate_jwt() function in your authentication server. You can implement the OAuth 2.0 flows, so the user would first log in and then request the access token using one of the flows, or you can issue the token right after the user successfully logs in (less recommended but practical in simple cases). To send the token, you respond with a 200 response, and in the response you include a payload with the JWT token. You may also want to include a refresh token and an ID token. So the response payload contains the following elements: {"access_token": "ey...", "id_token": "ey...", "refresh_token": "ey..."}. This is a standard response from an authorization server.
love your video.
Thank you for the nice feedback!
Please create a tutorial on deploying FastApi to aws or digital ocean.
Thanks for the suggestion! I'll start working on tutorials for AWS deployments soon!
👍
Always give me an error {
"detail": "Not enough segments",
"body": "Not enough segments"
}
Hi Luis in which context are you getting these errors?
@microapis: Before we get it started I would like to ask you to subscribe
also @microapis to a random person in the street: Before we know each other I would like you to make me a sandwich