I got the PingFederate running (from the docker image)and I can access the portal but it asks for a username and password.
I find online references that the default account would be "Administrator"/"administrator" or "administrator"/"2Federate", but nothing works.
I also deleted the file /server/default/data/pingfederate-admin-user.xml which should trigger to use the default account but no luck with those 2 credentials above.
After lot of research I found a guide that says that the default account is "administrator"/"2FederateM0re" and that one worked!
Related
I'm trying to setup and explore this firebase extension Trigger Email, as per other tutorial, you can use your personal gmail account (this might be where my problem starts) rather than using mail providers such as SendGrid / Postmark.
When I tried using it, I get the following logs on my document
I've followed workarounds here and in other sites however the problem persist.
Despite applying the following solutions I got from here, here as well and also here
Does anyone have like another workaround or documentation to follow on setting up? Thanks
The issue you are having is related to googles remove Less secure apps & your Google Account setting from our google accounts. Less secure apps was what enabled us to use our google login and passwords with their smtp server.
In order to use it now you must enable 2fa on your google account and configure an apps password. You can then use the apps password in place of your actual google password to connect to the smtp server.
Quick fix for SMTP username and password not accepted error
Working Solution in My Case
Apparently despite being Optional on the Extension Documentation, after you've enabled 2FA and App Password (selecting others on the device works for me). You have to configure the SMTP Password field as well to match the App Password you've just generated. It now works properly.
Can't login using Google Auth,
Error 403: org_internal
This client is restricted to users within its organization.
Go to cloud console (https://console.cloud.google.com/apis/)
APIs and services
Credentials
Oath consent screen
Ensure Application type is set to "public" and not internal.
Obviously assuming that you are creating an app that should be accessible outside your org. If this is related to testing and phones, it is possible to create testusers that are excepted from company policy rules.
The reason for this error is indeed because the Application type is set to "internal".
But setting it to public is not always the right answer...
Add "&prompt=select_account" to the authentication url. This will force the user to select the correct (organization-)account.
Without the parameter, Google tries to show the consent screen for the logged in Google-account, but as it is not an organization-account it will just display the 403 page without giving the user this choice.
https://developers.google.com/identity/protocols/OpenIDConnect#prompt
I had an Internal app that I was trying to authenticate with one of our YouTube channels using an organization account, and I was getting the same error:
Authorization Error
Error 403: org_internal
This client is restricted to users within its organization.
After contacting Google Workspace Support, they asked me to Change the restriction on it from Limited to Trusted.
Steps are mentioned in this support thread: https://support.google.com/a/answer/7281227
Open the Google Admin Console.
From the sidebar menu, choose: Security → API Controls.
Click on MANAGE THIRD-PARTY APP ACCESS button.
Hover the cursor over the required app and click on Change access.
Choose the option: Trusted: Can access all Google services
And save the CHANGE.
Once you've done, take note that there will be 24 hours of propagation on it before it gradually takes effect.
Make sure, for the browser you are using, that you have logged out of "All" Google account(s). This should force the "select account" windows to display.
We have almost exactly the same problem while trying to configure WP Mail SMTP for Wordpress.
The OAuth Client's Application Type has to be "Internal" so changing it to "External" was not an option for us.
Hope this helps.
I had the same issue and in my case was because the project didn't had a support email address set it.
I fix it by adding one on the Firebase Console > Project Settings > General under the Public settings section.
This error is most likely due to the configuration of your application in Google Cloud Platform.
Setting your application to "internal" is causing this error. Try making your app "external" in the OAuth consent screen, but make sure it is in a "testing" status. Then, add yourself to the test users. This configuration will work well for an internal, lightweight application.
Once complete, try to authenticate with the channel again.
I had the same issue with a project. The error only appeared if I tried to log in to my app while already logged in with an account outside the organization (worked just fine while logged out of all accounts, or while logged in with an internal organization account). I had to change the OAuth Client's Application Type from Internal to Public in the Google Dev Console.
More info can be found at https://support.google.com/cloud/answer/6158849?hl=en
Maybe you have another google email to login, not the correct one.
Recently I installed the Bitnami Wordpress canned deployment on Google Cloud Platform.
I can view the phpMyAdmin instance at a local address (http://127.0.0.1:8888/phpmyadmin/) but I cannot determine the username and password to log into the database cluster. I have tried the username specified in Deployment Manager, but the temporary password is not working. When I attempt to login, I receive the following error:
mysqli_real_connect(): (HY000/1045): Access denied for user 'user'#'localhost' (using password: YES)
I have tried to use various common passwords, such as root/root, with no success. If we assume the password is lost, how I can I figure out the password, recover it, or change it by using an SSH shell to the hosting compute instance?
Resetting password by supporting team if possible try
This issue seems related to phpmyadmin. I found this similar post where they stated:
This is asking for your MySQL username and password.
You should enter these details, which will default to "root" and ""
(i.e.: nothing) if you've not specified a password.
UPDATE
Have you tried to create a new user or change the password? Check this guide on how to do it.
Bitnami Engineer here,
As our guide mentions, once you create the SSH tunnel to access phpMyAdmin, you need to use the user 'root' and the password we configure at boot time (it's the same password we configure in the application). More information in our documentation
https://docs.bitnami.com/google/components/phpmyadmin/
Oh it's opened now, the user was (root) which it's not mentioned anywhere when i created the instance, the password is the one which generated by Bitnami when the instance is created on the bitnami platform lunchpad website.
the password is used for 2 users :
username: user
username : root (hidden) for new users who are decided to try cloud servers is not easy to figure this username and which password must use.
thanks for trying to help.
On March 7 (?) PayPal appears to have blocked access to existing Sandbox accounts (accessible through developer.PayPal.com). They require a login using my own paypal live account, then to "import" the existing Sandbox accounts.
But now, instead of having testers log into the Sandbox account, I have to give the credentials to my own live account. Obviously, that won't work.
The suggestion is apparently to create a "throw-away" PayPal account to "host" the existing sandbox accounts. This does not work (error: "Something has gone wrong. Please try again."). This might be because the Sandbox accounts have "already" been imported into the original account (my own live paypal account).
So I either need to "un-import" the accounts, then import them into a throw-away account, or to copy them from the live account to the throwaway account.
Has anyone managed to get through this? Or am I barking up the wrong tree?
(Note: PayPal apparently no longer provides technical support during business hours.)
I have feeling that you are near about, what you want. Actually previously there are separate section of sandbox environment. But now sandbox environment exists into actual account .
Firstly you need to login into your actual account of paypal then you required to import (means setup a new sandbox account in actual account) sandbox account.
Now you can login with your credentials. In my case its just simple but after reading your question its look you do some wrong things somewhere. please ask anything you want in comments or let we chat in chat-rooms.
I locked myself out of my Admin account on a client's site. I don't have access to the database because my client doesn't like to give that away, I need to upgrade my user account back into being an administrator. I've done it before, with something like wp_update_user() but I don't remember how & I can't find the online resource I used.
How can I upgrade my user account from being a user to being an administrator without knowing the ID of my account?
Thanks!