I found this one today! In our Portainer instance, our Docker images and stacks that have external ports all point to 0.0.0.0:[port]. When you click on it, it goes nowhere (of course).
The fix? In the menu on the left, select Environment-related and then Environments. Select the environment you’re working with, and in the main window where it asks for Public IP put the IP of the host (192.168.x.x, etc.).
We are finally moving towards implementing Okta FastPass in our Okta Identity Engine environment and have begun testing internally. A very early bug we have encountered is that when on our “VPN” (Twingate), the prompt for authentication hangs and takes several seconds to happen.
Digging through Okta Verify logs on the device yielded nothing and after searching around and searching deeper, I found an article on Okta’s support site that yielded the answer – we need to whitelist the domain authenticatorlocalprod.com in our VPN, specifically because that domain gets flagged in the DNS Rebind feature. Once we whitelisted the domain, Okta Verify prompts came through immediately.
We’ve begun rolling out Gemini and it’s been moving quickly in terms of updates and rollout. Here are our current settings that are letting users use it. Make sure your legal and compliance teams approve first!
Apps
User Access
Make sure you have a Gemini license, or your data may be used to train models
Service Status
Turn it on for OUs or just groups
Like many companies, my organziation uses Github and has multiple Github orgs under our umbrella. However, we don’t have Enterprise Managed Accounts for several reasons. But we have to closely monitor Github accounts due to SOX and compliance reasons and disable access when employees leave the company.
There is a round about way to do this with SCIM and Okta where you use an Okta app called “Github Enterprise Cloud – Organization“, enter your Github organization name, and setup SAML the way you normally would.
When I go to the Provisioning page and click to integrate the Okta app with the Github org, I frequently get an error saying “Error authenticating: Forbidden. Errors reported by remote server:”
After eons of troubleshooting, I’ve found the simplest solution is to make sure you are authenticated with Github, and then in the org you are trying to setup, go to this page: https://github.com/orgs/YOURORG/policies/applications/475360 and click the Approve button. What happened for me is that I wouldn’t see the Okta OAN integration app in our OAUTH apps page, and I couldn’t approve it. But it was waiting for approval. Going to that page above (which I could not find linked to anywhere) fixed the problem for me.
I’ve encountered this error in a few circumstances – users in Google Groups will have a red triangle and the text “Emails are Bouncing” that stops them from receiving any Google Group emails – definitely not good! I’ve seen this when former employees’ accounts are deactivated but not removed from Google Groups and then re-hired or activated later.
The fix is either remove and re-add them to their Google Group via GAM OR to have the employee go to groups.google.com, click the gear icon in the upper right, and click Global Settings.
From there, they should see under “Bounce Status” that their email is flagged as bouncing and a link that says “Resend request to recheck status” or something like that. After that, they’ll see a message that says “your email is not flagged as bouncing”. That’s it!
