Hello, Our team started diving into the documentat...
# gooddata-cloud
m
Hello, Our team started diving into the documentation of setting up an OIDC with Google Workspace. We were able to figure out the majority, but are missing one item. Where do we find our client id?
j
Hi Mark, you should get this when you are setting up your OAuth2 client, and depends on the OAuth2 client that you are using
m
Thank you. I'll have someone from our dev team look into that.
@Joseph Heun are we able to setup a time with the support team to help with this? we've hit a wall on what exactly we need to do
this is an error we also recieved
j
Hey Mark, sorry for the delay on this. I'm having trouble locating that traceID, would you be able to try and authenticate again? Once you have the error, could you copy the traceID here?
In order for us to schedule a call, we need to know exactly where you are in the process and which errors you are facing. Once we have this and are more familiar with your implementation and the current limitations/errors we can try and schedule a call to assist with specific steps.
m
Hi Mark, we were contacted by your Account Owner and we were able to find the logs. The error is in the endpoint of your PUT call, at the end
/alpha
is just an example, you must use your
/orgid
After that change, can you confirm if is working then.
m
Thank you! Just saw our Account Owner's email. we have another product launch his week, so we can dive back into this next week to see if it work.
Thank you for the help on this. I just directly messaged you both so I can pass along sensitive data pieces
@Joseph Heun @Mauricio Cabezas are we perhaps able to hop on a call now after we tried the above fix and now are getting
{"title":"Unauthorized","status":401,"detail":"401 UNAUTHORIZED \"Authorization failed for given issuer \"<https://accounts.google.com/.well-known/openid-configuration>\". Unable to resolve Configuration with the provided Issuer of \"<https://accounts.google.com/.well-known/openid-configuration>\"\"","traceId":"c8144663c38b9a82314e37cbf8fa6421"}
m
Hi Mark, Thank you for the updates, I am currently checking them and I will come to you with an update.
🙌 1
Hi Mark, I provided a possible solution by DM (I am bringing this becaus of visibility). Then you asked:
Thank you. We'll give that a try. Are we able to restore our site back to the default so that it works properly if we can't get this to work?
Can you please clarify what do yo mean with 'back to the *default*'?
m
@Mauricio Cabezas our site (https://lqdigital.cloud.gooddata.com/) currently looks like this. so wondering if we can revert our changes so we have a functional gooddata site/platform again
m
Ok, thank you. It seems you haven't try yet the last proposed solution, right? And, yes the issue must be solve in some point and you will be able to use your Site. As part of the troubleshooting, please, try the proposed changes/solutions
m
@Mauricio Cabezas doesn't look like we'll be able to do this update until late next week as need to focus on fixing bugs in a product launch we have this week. can we please have this reverted back to the original OIDC
m
Hi Mark, I am a bit confused, Are you able to access to https://lqdigital.cloud.gooddata.com/ with your user account? I have impersonate your organisation using our Admin user and I am able to access. Can you confirm please? If you are not able, can you allow me to impersonate your user?
m
@Mauricio Cabezas this is currently what our site looks like. it is showing up like this in incognito mode as well
m
Would you allow me to impersonate your user?
m
yes, please go ahead. thank you
m
Hi Mark, I can reproduce what you see. I will escalate this to our Technical Support team for a rollback to our Manage OIDC (for now). Now, I would like to know if this can wait until our Business hours (from 9 am CET), meaning around 7 hours more.
m
@Mauricio Cabezas yes, this can wait 7 more hours. would just like to get this resolved by tomorrow morning Pacific Standard Time (15 hours from now / 9am PST)
m
Hi Mark, thank you and our apologies for the inconvenience. A colleague will reach to you here with updates.
j
Hi Mark, I have jumped in as my colleague Mauricio is currently out of his office hours. I’ve gone ahead and re-enabled MANAGED_OIDC for you. You should be able to access your domain now with default GoodData Auth0. Please note that I have also set limit for 100 users as that is the limit rule for customers who are using our OIDC. I understand this is only a temporary solution and you will continue with implementation of your own OIDC soon. Once you start the next attempt, please let us know - we will switch off the MANAGED_OIDC setting again and set unlimited users on your domain.
m
Thank you. confirming that we see it working on our end again