I have setup two weblogic server version (12.1.3 and 12.2.1.3) in same host.
192.168.0.10:7001 and 192.168.0.10:7003.
I find that if I login one host and operate, I cannot login or operate in another host in the same client computer. It will redirect to login page. Is it normal? Would it affect the operation after production if accessing web applications?
Both domains use the same cookie name set by default for the admin console. Set a different cookie name for the second domain. Use the console and go to Domain -> Configuration -> General -> Advanced Settings and update the property "Console Cookie Name"
It because of the Console Cookie Name which is set in the browser.
We can resolve this issue if we change “Console Cookie Name” at Domain’s configuration advanced settings.
By default, domain’s Console cookie name set to “ADMINCONSOLESESSION”.
You can change the console cookie name for Admin Console by
Navigating
Click on Domain Name ==>Advanced ==> You will find the Console Cookie Name: parameter just change the parameter in one of the domain .
If you have more than 2 domain running on same machine .Change the Console Cookie Name different So that they don't conflict.
You can check the Console Cookie Name: set by the Admin Console by double clicking the address bar and then click on show cookie and site data and then click on host name .
Change the Console Cookie Name and then Restart the servers and then We will be able to open multiple Admin Console in the same Browser without any issue .
Related
I have an issue when I try to login to WSO2/myaccount or <WSO2IS_URL>/console. I can fill my login and password, but when after to have clic on submit button, I get an empty screen.
It worked the first time after a reboot of my machine.
Login & Password -> Submit
My personal page appeared
Logout
Login & Password -> Submit
I got an empty screen (blank page)
I have to say that I am behind an NGINX reverse proxy hosted in another machine.
I check in my browser and I get this message:
Uncaught (in promise) Invalid id_token in the token response:
eyJ4NXQiOiJNell4TW1Ga09HWXdNV0kwWldObU5EY3hOR1l3WW1NNFpUQTNNV0kyTkRBe.......
I checked my callback URLs for myAccount and Console SP and they are corrects.
I checked also the "Identity Provider Entity ID" for "OAuth2/OpenID Connect Configuration", and it is also correct.
Hereunder my deployment.toml file:
[server]
hostname = "<MY_WSO2IS_DOMAIN_NAME>"
node_ip = "192.168.xxx.yy1"
base_path = "https://$ref{server.hostname}"
offset = 0
internal_hostname= "identity"
[sts.endpoint]
idp = "https://$ref{server.hostname}/samlsso"
.../...
The "node_ip" value is the one for the NGINX reverse proxy hosted in another machine.
I tried many many things but I don't find where is the issue.
Any idea is welcome and appreciated. Thank you.
Seems your resident identity provider settings still set to localhost. If that is the case you have to change the settings as follows:
finally update changes by clicking the "update" button at the bottom.
This is the first time i am doing the deployment from my side and am new to AWS. I have a project deployed on Amazon AWS server for testing purpose. I have set the domain name as: https://domain.biz
I have a login page here where once the user logs in successfully i am setting the userId in the session and navigating the user to dashboard.
In the dashboard i have added a function to check whether session set with value of userId. If the session is not set then i am navigating user back to login page. This is to block the unauthorized access to site.
I am facing problem here. when i was working with the server before adding ssl it is working fine.after https://domain.biz session is working one page.and http://domain.biz works fine. When i have added domain to https then the session is not working. What is the problem here with AWS? Am i missing anything.
Check this : Session lost when switching from HTTP to HTTPS in PHP
Since codeignitor is in php, I suppose this thread could solve your issue.
I'm running three WebLogic 12 instances (different domains) in localhost, each listening a different port. When I login in one admin console, the session cookie for another gets overwritten, and I have to always re-authenticate when switching between admin consoles.
Is it possible to configure the cookie policy to avoid the conflict? And is it possible to do so with WLST in offline mode?
The best way is to set a different cookie per domain to avoid this issue. Use the console and go to / Configuration / General / Advanced and set the Console Cookie Name property.
I am trying to integrate facebook login in my django app but everytime I click on facebook login button it gives me an error
Given URL is not allowed by the Application configuration.: One or more of the given URLs is not allowed by the App's settings. It must match the Website URL or Canvas URL, or the domain must be a subdomain of one of the App's domains.
I my app settings my site url is
http://localhost:8000/
and also in my hosts file localhost have been mapped to 127.0.0.1
how to solve this as I have followed similar questions on stack but none helped a lot.
In your host file, set the localhost:port to the domain you wish to log in from.
Then, set the Facebook app's domain to the domain you've pointed your localhost to.
I have this weird problem in IE 9. I have a site which allows a user to login and can also be logged in by a separate website using web service in the background. When logged in, a cookie is created. In fiddler, I can see the user has logged in to my site from the third party website and the cookie is created. The third party site makes an ajax call and the cookie is created in my domain.
But when I click on a link to my site from the third party site, the login page is displayed again. I wrote a debug code that states in the page that the cookie does not exist but I can see in IE settings that the cookie does exist. The cookie expires in 24 hours.
How do I fix it? By the way, it works fine in most other browsers including IE8, IE7, Chrome.
This is similar to - IE9 Separate cookies for third party request - but there is no response there.
There is a limitation introduced in IE 9+. It isolates different zones to access each others' data. For example if a cookie is created in example.com for domain:example.com, a.example.com cannot access the cookie if their zones are different (one is intranet, one is trusted, etc.). You can check the zones in Internet Option -> Security tab.
For more information check Cookie Sharing in Cross-Zone Scenarios