I installed Dspace multiple time on different windows servers.
I worked perfectly but i faced a fundamental problem in user authentication.
When I register a new account, it was made correctly.
the main problem is on the login/logout process.
When i logged in, then would like to logout,after a short refresh, the header of the Dspace was not changed the user status and continue to display my username instead of login button. I notice that when the page refreshed manually , the problem was solved.
another problem is that when i try to login from other browsers, before authentication, I see my username or other username(unknown) on top of the page.
Please inform me about the potential problems and solutions.
It's the navigator cache. It is harmless
Related
I am working in one project in which I need to integrate Google One Tap Login which show All accounts list that were currently logged in into browser.
One Tap Login Iframe is adding successfully in localhost environment but With the use of same PROVIDER_ID, When I deploy my project into server with staging url.
I got Issue with Open Iframe. It is always show error like "noCredentialsAvailable: No credential is available for the current user." But I already have login with two accounts in gmail.
I can't understand this kind of behaviour of Iframe.
Another question of StackOverflow say's that put button of Google for login via google. but I want to resolve this issue.
Is there any missing code from my side ?
Same Prvider ID is used in Localhost and Staging(subdomain) Still Error is occur.
Our web app allows users to log in via Facebook. Technically, we are using Facebook OAuth2. We have implemented this login process two years ago. It worked fine until 13th November 2015 but since that day it does not. When our server sends the request
https://graph.facebook.com/oauth/access_token
with appropriate parameters (client_id, redirect_uri, client_secret, code), the response from Facebook has HTTP status 400. The response body is a HTML page saying "Sorry, something went wrong".
On 13th November, there was some problem on Facebook probably.
I have found the following message:
http://www.independent.co.uk/life-style/gadgets-and-tech/news/facebook-down-site-breaks-for-many-people-though-not-for-everyone-a6732906.html
However, our server still gets this error response after a week. We have an instance of the system deployed in the production environment and one more instance in the test environment (with different Facebook account, i.e. with different client_id and client_secret). Currently, Facebook login works fine in the test environment. I am not sure if it worked on 13th November.
Do you have any experience with recovery from such problem? Why does Facebook login work in test environment and does not work in the production environment in the same app? Why did the production instance break on a particular day and is still broken a week later?
Thanks for any help.
I had the same issue. I believe that the issue stems from passing in invalid scope in your authentication requests. Try removing the scopes in your authentication request to see if that works.
One more corner case I found in 2022:
In the App Dashboard, if you choose Facebook login for Business, same error happens. It will go away as soon as you select Facebook Login one.
Finally, the issue was resolved by restarting the servlet container (Tomcat 7). However, I have no idea why.
All of this is using exclusively the login button. Not the API serverside and not FB.login(). It would work for me sometimes and sometimes not and I couldn't figure out why. I would open a new window and it may work, or may not - but it seemed like once broken it was broken.
There appears to be an issue when using the Chrome 'Device simulator'.
Looking at the SDK Javascript (that's to say the SDK that the Facebook Login button uses) it checks to see if the device is a 'touch' device and if so it will use the m.facebook.com domain when requesting the oauth token.
This domain fails m.facebook.com:
However if the mobile device mode isn't activated when the page loads then it uses www.facebook.com and succeeds:
So for me the current workaround is:
Assuming you are developing with the console active.
When you need to reload your page press Ctrl + Shift + M to deactivate the mobile device mode.
Refresh the page
Once the button has initialized press Ctrl + Shift + M to reactivate it again.
If you see m.facebook.com then you didn't do it fast enough, or maybe you're using something like Angular with hot reload and you need to manually refresh.
I got an problem after i create and APIs on Google Developer Console and enable the GCM service,
but i want to add an server key at Credential next to APIs on left hand menu.
But it show me You do not have sufficient permissions to view this page.
Below are the image:
Is that any config i need to add?
I did follow what You do not have sufficient permissions to view this page to clear cache and use incognito mode to login, but still not work.
EDIT
Some time i relogin it work back, when i click to another side and click back it show the error again, and my solution is go to Credential than use top right corner account to logout and relogin , let it redirect you back to Credential, than it work. So is there any solution to fixed it permanently without relogin?
Thanks
It because of you have logged in multiple devices. so u have to log out from all devices. to do this go to gmail.com and log in using your email and password. and scroll down . you can see Details link . Click that link.
it will open new window. there u click
Sign out all other web sessions. than clear history. than do login and try . it will open without showing error.
I got the same problem. After following the below steps it got solved. This may help you as well.
Click on Apis under Api & auth
Click on "Google Play Game Services".
Enable the service.
Optional: enable "Google Play Developer API" as well. Most of the time it will enable by default.
I am facing the same issues.
Try using another browser like firefox - sometimes it works.
but after awhile, same error pops up.
Having the same issue as with you regardless what api i enable.. have tried all the suggestion posted earlier. but none of them worked, but when i tried to change my i.p.. using a vpn. and tried to access it.it worked, i can create or view my api now,tested it with other gmail account to confirm and started from scratch. to my surprise i didnt encounter that issue im having for hours.. no idea why my i.p is being rejected when accessing the credentials area..
I've resolve my issue, it's about the ISP you are using. I tried 3 ISP's and 1 of them got a success all the time, I don't have any permission error.
I have had the facebook connect set up for over a few months and have done a lot of testing on it and everything seems to be working correctly. Suddenly when I try to login using the php facebook sdk I get redirected to the following page https://www.facebook.com/help/258359927634494
It seems to let me login on occasion, but it usually redirects to this page. I assume my app was reported however we only have a few test users at this time as we are in beta and I stopped my app from asking for repeatedly for post permissions a while back as soon as I was aware it was doing that. What can I do to clear up the report?
This message appears when an app loads the login dialog many times in a short duration. Make sure you are only loading the dialog once per user. Until this redirect behavior is tweaked to be me more lenient, try waiting ~30 seconds between tests.
So we are using ADFS in a public facing SharePoint 2010 site. One of the supported logins is via Live ID. We have found that if a user logs into Live ID site like Hotmail prior to reaching our site, the following happens:
Our site thinks that the user is not logged in because the ADFS LS cookie is not present
When we click on Sign In and ADFS redirects us to Live ID, the Live ID login process detects its cookie and automatically logs us in using the prior user's email. We actually want to use another email address.
Even if we clear our cookies, the above behavior persists
We have tried the following on Windows 7 successfully:
Clear the browser cookies
Delete all files from %userprofile%\AppData\Roaming\Microsoft\Windows\Cookies\
And then Live ID correctly asks the user to login.
However, the above folder does not exist in a Windows 8 computer where this behaviour can be reproduced in IE 10.
So I really need to know the name and location of the Live ID cookie so I can hunt for it and destroy it to get the sign in prompt.
The ideal solution is that ADFS destroy the cookies correctly. The ADFS team is building a diagnostic page to delete their cookies but I do not think they will be able to destroy the Live ID cookie as it is not from their domain. If I can find its location, we can live with manual instructions for now.
Update
Found an answer. The trick is to go to live.com and click on signout first and then go to the SharePoint application. Not the best solution, but it works.
Update Found an answer. The trick is to go to live.com and click on signout first and then go to the SharePoint application. Not the best solution, but it works