I need some help in Navigating through multiple project pages.
I have one parent and 3 child projects. I am using my custom login page which is in the parent project. Then i am accessing the login page from one of the child project. Authentication is done by default user source for now using system.security.validateUser(userName, passWord, userSource) but in future we have plan to I love you use Microsoft ad.
I am checking authentication and then have custom session variable updated with user details. Before opening any page in all project I am checking those user credentials if those are not null.
Now I want user to login one time from the login page from any child project and then reach home page where I can have cards for each project and user can select any card to go to the home page of that project. But the custom session variable of other project are not getting updated so user is not abkle to access that project.
What will be the best way to handle this scenerio. Should i change my login approach or should i try to use message handler to send the custom session variable value to other projects in the gateway or should i try some database approach.
Please let me know if anyone have any idea on this?
I am using system authentication and default user source idp for validation. For multiple project We have requiremnt for each project for individual functionality like production maintainance e.t.c. So that in future updating of modifying one project dont affect other projects. but high level manager should have access to specific pages in all project.
For this i was thinking if there is any way to maintain the login credentials across project with just one time login?
Thank you so much for your response.
I have removed my custom login page and now i am using the default ignition idp and ignition login. I can navigate between pages of different project. But now i have problem in the log out. When i navigate to other project and od the log out using system.perspective.logout() my session is getting logged out for that project only not the main project from where i am navigating to the second project. Also when i click on back to go to login page again when i log in the page from the second project from where i had logged out is opening again as it was the url i had at the time of logout.
The behavior i want is that i have one main project where i have home page to navigate to other projects. So when user log out from any project whether it main or other projects. all project session should be logged out and when user try to log back by clicking back to get to login page then after login the home page of main project should open.
My apologies if i am not able to explain my situation correctly please let me know if the explanation is not good enough. Thanks again for all the help here.
I had a similar problem, with a couple different projects that people were often switching back and forth between. I probably would have developed them as parts of the same project, but it was like that when I started working here, and it would take significant effort to combine them, and people were already used to the navigation structure of each project.
What I ended up doing was creating a "wrapper" project that creates a side menu navigation between the projects that toggles their display within Inline Frames. Whenever a user logs in under one of the projects, a database entry logs their host and the time. Each project invokes a script every few seconds when not authenticated to see if that host logged in within the last few seconds, and if it did, invokes system.perspective.login() which automatically logs them into that project.
Not terribly elegant, but it works, and creates the illusion of a single project.
I have found somewhat working solution for my problem. By using same idp i can login to all the project seemlessly and for log out i have used session event message handler to logout the current user only. and then call the message handler on all project session event and if the user is active log him out.
