Develop Reference

OKTA AWS CLI Using Python to Connect to Athena

My company uses Okta Authentication for all corporate applications. Is there a way or a workaround to circumvent the OKTA Authentication while connecting to AWS Athena? I'm trying to automate a Python Script that connects to Athena and it requires me to Okta Verify every time after the short-lived token expires. However, Google Suite (Docs, Sheets, Drive) API's doesn't require this type of AUTH verification method and it never requests one when I connect Python to Google Suites although our Google Suite use Okta Authentication for login.
Any help or references would be much appreciated. Thank you!

OKTA Sso python

Hi I want to access an application that is behind OKTA sso. I am using python requests module for accessing the application. Before Okta I was able to access the application with userid and password from my python script. But after okta the script is failing to access the application.
what modification I need in my Python script using requests module

From what I understand, there is a big chance you want to access an application using Okta issued token.
You need to reach out to the application developers to identify how to properly retrieve a token. There are lots of ways to authenticate using Okta and without more information it's gonna be hard to help you out.
Once you have all those information you should be able to use any python module providing requests authentication classes for the authentication flow that you have to use.
Disclaimer: I wrote requests-auth providing Okta authentication classes that can be used with requests (nominated in the Okta developer community award).

openid connect provider and client example in django

I need to build a Django web-app. My web-app needs to support authentication and authorization using OpenID Connect. It is my first time doing this. Is there a free Identity Provider to test my application or do I need to write the provider and the client? My task is to write only the client that connects to the provider. An example would be great or some course/tutorial I can use to learn how to do this.
Maybe there are no good examples in Django but I know ASN.NET and Java so those examples could inspire me as well.

There are a bunch of OpenID Connect providers you can use to test your client: you can sign up for a free Auth0 or Okta developer sandbox, download and run IdentityServer locally, or try the OAuth2 Playground.
As for writing the client. Please don't write your own. There are a list of libraries from the OpenId Foundation. I've used pyoidc for a non Django application, you could hook that in to your app, or use one of the Django specific OpenID Connect libraries.

checkout this example using both provider (django app using django-oidc-provider package) and client (using JS).
https://django-oidc-provider.readthedocs.io/en/latest/sections/examples.html

Using Windows Credentials to do Basic Auth in Python

I am writing a Python application to download csv files through an API on an internal server, by sending GET requests. When testing the requests through Postman, I was able to use Basic Auth along with my Windows credentials to generate a token and authenticate on the server.
Now when it comes to the Python application, I obviously don't want to hard-code my Windows credentials into the app, nor do I want to use the Basic Auth token that was generated (maybe I'm wrong, but this still seems like it would not be a very secure thing to do as I believe the token is a direct hash of my credentials, not to mention when I change my credentials I would have to go and update the token as well).
What I want to know is if it is possible to automatically use the windows credentials from wherever the program is run, in order to authenticate against the server. I tried using NTLM, but unless I am misunderstanding this would still require my credentials to be coded into the app, and from my testing it looks like the server only supports basic auth and not NTLM directly.
I am very new to authentication in Python (and in general), any help would be appreciated.

Google App Engine Federated Authentication - migrate from OpenID2

We have an application deployed in production environment running on Google AppEngine with python2.7 and NDB.
It uses the Federated Authentication via OpenID implemented according this article: https://cloud.google.com/appengine/articles/openid
The Users API from AppEngine is used for authentication (e.g. users.get_current_user(), users.create_login_url(federated_identity='https://www.google.com/accounts/o8/id') for Google login, etc.) - exactly as it is described in the main.py under Examples section in the article above.
Recently we are receiving a message during authentication:
OpenID 2.0 for Google accounts is going away.
Developers should migrate to OpenID Connect by April 20, 2015. Learn more.
I see that there is a documentation for "Migrating to OpenID Connect (OAuth 2.0 for login)" at https://developers.google.com/accounts/docs/OpenID#openid-connect
Probably every single person who uses Federated Authentication on AppEngine will face now the problem of migration... and will need to preserve the user data bound to the existing user identifiers which the Users API provides.
We must preserve the usage of Users API - as it is used all over the application.
Does Google plan to offer an alternative to the single line code users.create_login_url(federated_identity='https://www.google.com/accounts/o8/id') on AppEngine to make the port easier?
Is there an example source code of how to migrate the Federated authentication on AppEngine in Python to the new OpenID Connect?
Is there a compatibility layer for Users API with Federated authentication planned to be provided?