Hi All We have upgraded the production server from Appian 7.6 to Appian 7.8

amqashqari over 9 years ago

Hi All
We have upgraded the production server from Appian 7.6 to Appian 7.8 on 06 Feb 2015.

We have configured the IIS with Jboss.

Appian is working fine in IE and Firefox, but we are unable to access the Appian using Chrome browser.

Using Chrome we are able to get the login page, but after providing the correct credentials, we are not able to login. We are getting the below error:
401 - Unauthorized: Access is denied due to invalid credentials. You do not have permission to view this directory or page using

the credentials that you supplied
More Details:

Windows OS - Windows Server® 2008 R2 Enterprise
Appian - Appian 7.8
Jboss - Jboss 6.3 GA
IIS - IIS 7.5

attached the application server logs- "production_chrome_browser_issue_log.txt".

any help would be greatly appreciated

production_chrome_browser_issue_log.txt

Discussion posts and replies are publicly visible

0 mathanap over 9 years ago

Hi Amjad,

Hope you are doing good.

In the shared log, we are unable to find the 'caused by' trace. So can you please attach more log details
BTW, adding your domain name(example.example.com) to the embedded interface - allowed origin in the admin tab might solve the problem temporarily.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 jims419
Certified Lead Developer
over 9 years ago

Are you accessing the site from the actual server name and port defined in custom.properties? I've seen this type of behavior when trying an alternate url like "localhost"
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 9 years ago

In addition to review the suggestions posted above, can you check if this environment uses Kerberos/SPENEGO SSO? To be able to use Windows Authentication on Chrome you'll need to configure Chrome for that purpose

www.microhowto.info/.../configure_chromium_to_authenticate_using_spnego_and_kerberos.html
productforums.google.com/.../
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 amqashqari over 9 years ago

Thanks Jims419 for your response, we doubled check the custom.porperties and we are using the correct server name.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 amqashqari over 9 years ago

Thanks Edurdo.Fuentes for your response. I reviewed we don't use SSO and only configured LDAP .
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 amqashqari over 9 years ago

thanks Mathanap for your response , After adding domain name(example.example.com) to the embedded interfacet chrome starts works properly .
but as you said this a temp solution , we specious it could IIS Configuration issue after upgrading to Appian 7.8.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 mathanap over 9 years ago

It seems that there is some issues related to Server name/IP address. Is there any recent changes to IP or Server name?
Are you experiencing the same in other environment? If yes, then can you please double check Jims419 suggestion in other environment as well.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 amqashqari over 9 years ago

the issue happens in all environments that have been upgraded to 7.8 . there is no changes happened in names or IP dresses
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 amqashqari over 9 years ago

We used to define the port (443)in custome.properties because we configured https in IIS.
We were recommended to remove the port number from the custome.properties and it is not necessary when we use the ports 80 or 443.
After that chrome works properly .
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 mathanap over 9 years ago

Good to know, that we found the root cause of the problem. Thanks for posting it.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel