Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
9 replies
Subscribers
7 subscribers
Views
3243 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
We have a 7.8 environment and are having issues with the default landing page, s
brettr
over 10 years ago
We have a 7.8 environment and are having issues with the default landing page, specifically when users log out and log back in. When a user logs out, they are taken to /suite/ and when they attempt to log back in they are shown a 403 - Forbidden Error. The 'Return' link in this error points to the URL <environment base url>:<port>/suite where the user is able to log in again, but then shown again to the 403 error. The User Start Pages in the admin console seems to be set up correctly. The default is <environment base url>:<port>/suite/tempo/ and I have even tried adding the same URL for our All User Group. Below is the error that we are receiving in the log when a user attempts to log back in.
2015-03-15 20:23:28,153 [ajp-/0.0.0.0:8010-4] ERROR com.appiancorp.util.BundleUtils - Cannot retrieve the value for key "conf.defaultLandingPage.DEFAULT_LANDING_PAGE.instructions" from the bundle.
2015-03-15 20:23:28,155 [ajp-/0.0.0.0:8010-4] ER...
OriginalPostID-142036
OriginalPostID-142036
Discussion posts and replies are publicly visible
0
brettr
over 10 years ago
...ROR com.appiancorp.util.BundleUtils - Cannot retrieve the value for key "conf.defaultLandingPage.DEFAULT_LANDING_PAGE.label" from the bundle.
Does anyone have any thoughts as to what might be causing this?
Thanks!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 10 years ago
What's the value of the User Start Pages in the admin console?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
brettr
over 10 years ago
Hi Eduardo, since our environment is accessible through the web, I am going to replace that actual values with generalized ones.
dev.ourdomain.com:9123/.../
That is not the exact port we use, but it is one that is non-standard. If we copy that URL into the address bar, we are able to access the environment correctly.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 10 years ago
You can't use URLs of that type in the User Start Pages, the start pages is to specify what tab from Tempo you want to display, or what record, etc. and it takes a RELATIVE PATH.
1. If you want all users to be redirected to Tempo when typing /suite/ then you configure this ONLY in custom.properties (in the server) by leaving this setting blank or commented out
conf.suite.DEFAULT_ENVIRONMENT=
2. If you want "/suite/apps" to be your default one when users hit /suite/ then you configure this ONLY in custom.properties (in the server) by setting it to apps
conf.suite.DEFAULT_ENVIRONMENT=apps
3. If you want your users to be always directed to the Tasks list on tempo when accessing /suite/ then you configure this in the Start Pages as /suite/tempo/tasks/
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
brettr
over 10 years ago
On the User Start Pages, I receive an error if the base URL does not match the correct URL for the environment. If I change the current value to
dev.ourNEWdomain.com:9123/.../
or
/suite/tempo/
I will get a validation error saying:
"The URL is invalid or has an incorrect base URL. The base URL must be
dev.ourdomain.com:9123/"
It is also my understanding that the DEFAULT_ENVIRONMENT value, in 7.8, will get trumped by the new User Start Pages. Just in case it doesn't, I did verify that we did not add that setting to our local.properties in the ACM and that it is not set in custom.properties.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 10 years ago
My bad, you're right, it's absolute not a relative path.
Basically what I was trying to say is that you shouldn't just use
dev.ourNEWdomain.com:9123/.../
you need to use something else after the word "tempo" to specify where users should land, either tasks, reports, news, actions, etc.
If the purpose of simply using /suite/tempo/ was to make Tempo the default environment then there's no need, as you mention, not editing DEFAULT_ENVIRONMENT already sets the default to Tempo.
Start pages are to specify more than just /suite/tempo/ (which results in News being the landing page). For example, a lot of people choose Tasks as the start page which is:
dev.ourNEWdomain.com:9123/.../assignedtome
Using /suite/tempo/ is redundant.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
brettr
over 10 years ago
Apologies for the delayed response. I have tried your suggestion by using assigned tasks, reports and even record types. Any time the user attempts to log back in form /suite/ they will still receive the 403 forbidden error. I have even tried adding and removing the DEFAULT_ENVIRONMENT setting to custom.properties, but no luck.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
brettr
over 10 years ago
Solved!
It looks like it was actually an issue with our Apache server being configured incorrectly. For anyone that runs into this,
We had an entry in httpd.conf:
<IfModule dir_module>
DirectoryIndex index.html
</IfModule>
This was causing all directories to navigate to index.html which does not exist (I am assuming). I changed the entry to the following, and we are no longer experiencing the issues.
<IfModule dir_module>
DirectoryIndex /
</IfModule>
I appreciate all of your help and effort in looking into this and offering suggestions, thank you!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 10 years ago
Great news! Thanks for sharing.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel