Postman still sends to old sever although I updated its' variable. It works correctly on the web app. I've changed the server & linked the new server with the same sub-domain and deployed the same old app.
The windows app
The web app - works fine and it responds as it should
I changed the variable of the URL
I tried to create a new environment - didn't work
I tried to remove the entire workspace - didn't work
I un/re-installed the app - didn't work either
Is there a cache in the app itself or something to clear it to get the new value?
appreciate your help. T^T
An example to clarify my issue:
I have a subdomain: backend.mydomain.com
I've linked my server IP 152.50.133.60
so backend.mydomain.com points to -> 152.50.133.60
I made backend.mydomain.com free again to use it on a different server
Now I linked my new server IP 163.33.80.92
Now my backend.mydomain.com points to -> 163.33.80.92 & it works fine on (the postman web app & chrome)
When I try from PC app it still has the old value as in console pic
It worked after:
Signed Out.
Made a request not signed in.
Signed in again, then made a request it worked.
No clue why though!
Related
One of my old website is running TYPO3 v4.5.
I bought a SSL certificate and my sys admin installed it on the server.
the front-end is running well on https
tha back-end login form runs weird : one time my login/password are ok, but sometimes it doesn't allow me to enter the back-end.
It is totally random and in Firebug, I have no clue in the console or in the network tab to help me. Same behavior for Chrome, FF or IE.
I tried a lot of parameters :
[BE]LockSSL = 1
[SYS][reverseProxyIP] with " ... "
[SYS][reverseProxySSL] with " * "
[SYS][cookieSecure] = 1
I event tried a lot of different combinations, with no success.
Please notice that I also get a TYPO3 6.2 website and those parameters work perfectly on it. I guess that I am missing somthing for v4.5 ?
Check the BE cookieDomain configuration!
I inherited an existing project without its development environment. I have UAT code and a backup of the Production database. I can run up the site locally via Visual Studio but have hit an authentication problem trying to setup a fresh standalone DEV server on AWS (single server, no load balancer). The doco indicates the Prod server is a dual server setup with a load balancer.
The front end site pages do display, although some search is not working. On trying to log into the backend pages, Chrome returns "The xxx page isn't working. xxx redirected you too many times." Using developer tools, I can see the page redirects back and forth between SWT?realm=... and sitefinity?wrap_defalted=true&wrap_access_token... On the second redirect response header there is "X-Authentication-Error:Missing configuration for the issuer of security tokens 'https://xxx/Sitefinity/Authenticate/SWT' "
I tried different values in the web.config lines:
<federatedAuthentication>
<wsFederation passiveRedirectEnabled="true" issuer="http://localhost" realm="http://localhost" requireHttps="true"/>
<cookieHandler requireSsl="false"/>
</federatedAuthentication>
but that actually made things worse so I have reverted.
I checked all the settings mentioned in http://docs.sitefinity.com/administration-switch-to-claims-based-authentication and they seem to be set correctly. I don't really know what else I can check to get this working.
I found http://docs.sitefinity.com/administration-configure-security, but it does not seem like these settings are set (I don't have access to Prod server so can't confirm if it is actually setup with load balancing). I am currently using a 30 day trial license so am not sure if this is contributing to the problem. The official license is in the process of being transferred by the client. The domain name associated with the official license would be different to the domain my new server is currently running on.
I am also running version 8 code on a version 9 install of Sitefinity. I wanted to get it working before I tried to upgrade the code. I think there was also an assembly load to manifest mismatch when I tried upgrading my local version.
Found the solution: Don't mess with the SecurityConfig.config file.
<securityTokenIssuers>
<add key="B886AA7BFB5515BA63F577A44BBEB5C7AE674035514D128BC397346B11F4C97A" encoding="Hexadecimal" membershipProvider="Default" realm="http://localhost" />
</securityTokenIssuers>
<relyingParties>
<add key="B886AA7BFB5515BA63F577A44BBEB5C7AE674035514D128BC397346B11F4C97A" encoding="Hexadecimal" realm="http://localhost" />
</relyingParties>
Even though it is running on a server, the above lines should still point to localhost. It seems like these only need to be edited if you have a multi-server setup with an entirely separate STS.
I initially changed it to match the new domain name, but after some experimentation around adding localhost and HTTP variations, it seems like it works best with just localhost.
Even when I changed the web.config entry above to use the new domain as the issuer instead of localhost and the SecureConfig.config to specify only the new domain as the realms, it didn't seem to work. I guess the authentication must try to hit localhost specifically.
Our ServiceNOW instance recently got upgraded from Eureka to Geneva.
MID Server status became down and the version does not match the Build number in the stats.
I was told that the MID Server will auto upgrade which didn't happened. I am using a proxy server to connect, when I tried communicating with the instance through the server it is working however I assume the service or application installed is not able to communicate with the instance.
I created a new service and it worked perfectly for 1 min however after that the status of it became down.
Then I tried changing the configurations of old services however no good.
Now the services are running fine however in the config file in the mid_sys_id section mid server details not getting populated and the status of the MID Server in the instance is always down.
Do I need to change any properties in the instance?
Since I use proxy server do I need to remove the comment line of the auto upgrade through proxy section or can I leave that blank?
What is the issue here? Why my MID Server is not getting upgraded? Kindly help me.. If possible an explanation with screen shot would be much appreciated.
If you're on Geneva, you should be able to simply go to your MIDServer listing, from inside your instance, click on a MIDServer, and find 'Upgrade MID' in the Related links section. That should start an upgrade for that MID Server. If it fails, there should be an entry in either the ServiceNow logs or the MID Server logs with more information why it failed.
I am using a java raw HTTP client to connect to Shopify API (specifically, using Play Framework with the non-defualt sync driver which is actually the JDK's default driver).
My application usually manages to connect successfully and convert the temporary access token into a permanent one by calling the /admin/oauth/access_token endpoint.
However, sometimes I get this error result from the API:
Generic Error(400)
{"error":"invalid_request"}
I haven't been able to reproduce the issue with my test stores - I've tried installing a fresh store, reinstalling existing stores after uninstalling, I'm not sure why this call sometimes fail and how to debug it. The API call still continues to succeed for some stores using our application.
Some things that I am doing:
Even if the URL of the store is on a custom domain, I'm always using the https://foo.myshopfiy.com/admin/oauth/access_token URL and not the URL of the custom domain, to prevent a redirect.
I am always using an https URL and never an http one, again to prevent a redirect (we noticed a few issues with redirect with the Java HTTP client, so we aim to have zero redirects)
A thread I found about this error suggest possible problems with our SSL certificates, however I don't think this is my problem because some requests work for us, and the result of running openssl on our machine does't show any issues.
How should I proceed? Open a support ticket with Shopify?
FYI, I see that this specific problem only started yesterday on Feb 19 2013, so it might be a temporary issue.
FYI, the problem was caused by reusing a temporary access code.
Our fault - Shopify could have been more clear in their error message though.
My Kohana app runs perfectly on my local machine.
When I deployed my app to a server (and adjust the config files appropriately), I can no longer log into the app.
I've traced through the app login routine on both my local version and the server version and they both agree with each other all the way through until you get to the auth.php controller logged_in() routine where suddenly, at line 140 - the is_object($this->user) test - the $user object no longer exists!?!?!?
The login() function call that calls the logged_in() function successfully passes the following test, which causes a redirect to the logged_in() function.
if(Auth::instance()->login($user, $post['password']))
Yes, the password and hash, etc all work perfectly.
Here is the offending code:
public function logged_in()
{
if ( ! is_object($this->user))
{
// No user is currently logged in
url::redirect('auth/login');
}
etc...
}
As the code is the same between my local installation and the server, I reckon it must be some server setting that is messing with me.
FYI: All the rest of the code works because I have a temporary backdoor available that allows me to use the application (view pages of tables, etc) without being logged in.
Any ideas?
I solved the problem (DUH!).
The answer was that the cookie.php config file had $config['domain'] = 'localhost'. Setting this to the actual domain that the app is installed in magically made my life happy again!
Thanks everyone for your help and interest.