[feature-1967]Customizing Perspective Login Page

[mitchell-ACS]

Is there a way to customize the Perspective login page?
At this point, all I really need is to make it use the project Title instead of the Name because the project name is Some_Project, and the project title is Some Project.
Also being able to display a company logo would be nice as well.

[paul-griffith]

Project title being displayed there is coming - hopefully 8.0.2, although it might miss the cutoff

I could see us adding an image, although that’s no guarantee - I’ll file a ticket to see about it. It’s a bit tricky if it’s the overall perspective project required auth - at that point, we haven’t really loaded in all the info about your project. It’s much easier to style the login “upgrade” page you get from the app bar → sign in button.

[ankitkarwa21]

I see the project title is now being displayed.
Do you have plans for other customizations?
Project image?
Also, maybe a company logo on the left hand side?

[ankitkarwa21]

@paul-griffith Would appreciate any update on this.

[paul-griffith]

Project title updates should go into 8.0.4 - I was in charge of the original changes, but after they got rejected by QA I hadn’t gotten back to work on them due to higher priority issues. Last week I finalized the changes, so it just needs to be approved and go through QA, which will likely happen before the 8.0.4 release cutoff.

Additional customizations are not currently planned, to my knowledge - but that’s something that would be good for ideas.inductiveautomation.com

[ankitkarwa21]

Thanks @paul-griffith

[roberto.camp]

I've been thinking about this, because it's something we'd like to do also... and it occurred to me after reading this thread:

WebDev login, and forward to user specific project

What does ‘their project’ mean? A Vision project? How is that going to work - without applets, you will have to download a JNLP (if in 7.9) or the native client launchers. The only way webdev would work to form your own login page is if your entire “project” was also hosted in webdev.

Wouldn't a simple solution be to allow the possibility for creating your custom login page in a project of it's own (or in a more complex project), creating a custom username/password field entry and then using an "improved" version of the "system.perspective.login" script function to pass the parameters entered by the user (user/pass) and forward them to Ignition's configured idP? thus starting a session and skipping the normal login screen?

Not sure if I'm missing anything or if this a feasible idea, but we'd like to be able to make a custom login screen and then distribute users to the relevant projects based on that. I've been able to make a version of this, but I'm not entirely happy with it...

[marioishikawa]

Can this be done with custom html somehow?

[larryjones]

Roberto,

Will you share some details of your custom login screen? We would like to develop a login screen that has a dropdown list of users from AD so that the user can select his username, enter his password, and press a login button. I’m not even sure there is a scripting function for Perspective that can be used to login a user.

[roberto.camp]

Hi Larry,

Sorry for not replying sooner, I’ve been working on other things that do not require Ignition and have therefore not been lurking in the forums lately.

The solution I discussed here didn’t work out. We ended up making a custom middleware application that serves as a gateway of sorts. We use the IDP features from Ignition and the middleware manages the redirection to the appropriate projects. Ignition manages the permissions based on the user that logs in. It’s a bit more complex that what we’d like, but it works well so far.

Hope this helps.

[Carl.Gould]

I just wanted to chime in here to say that customization of the sign-in page is being done as a broader effort to improve co-branding of some of the more heavily Ignition-branded UIs (login, loading page, etc). I’m updating this topic title to track the correct internal issue number.

[tyler.robertson]

Just wanted to add that for me, the customization of the front page is some branding, some function. That I can make front and center, the only thing on the page, a reminder to users that their login is case sensitive.

[tupanaster]

Does that mean that a component will be made for logging in instead of providing a function for it?

[jlandwerlen]

@tupanaster see if this post will answer your questions,

New Feature - Ignition & Perspective Co-Branding

Hello everyone, I’m happy to announce the release of the feature of Co-Branding for Perspective that will be available on the nightly builds. The purpose of this feature is to give designers the ability to add branding to their projects for end users. The feature can be found in a new category in the Config section - Perspective > Branding Customization. Co-branding is currently a Gateway wide setting that will affect all Perspective projects. [gateway_page] Brand Theme Customization Backgro…

[David_Nicks]

Not sure if this is along the same lines or not - but is there a way to extend the branding customization to the gateway status and configuration pages? We have a 3-tier environment (DEV/TEST/PROD) and it would help if the gateway pages were more distinct between environments. We've had issues where someone made config changes in the wrong environment because they had both open at the same time and lost track of which was which.

Alternatively, is there a backdoor route where we could customize the CSS used to generate the gateway pages?

[bkarabinchak.psi]

I am learning more of the network IT side of things and recently tried using DNS to handle this so I go to devIgnition.psi.com for the dev one, stagingIgnition.psi.com for staging and prodIgnition.psi.com for the production one. Then I can look at the URL to see which one I am in and I can read it, I don't have to memorize what IP is what.

[paul-griffith]

Deployment modes are going to be a first class concept in 8.3, with associated UI around every time you're making changes.

[Baskar_Arumugam]

Hello,

I am trying to replace the default Perspective login page in Ignition 8.1 with my own custom login view, but I am running into issues and would like guidance.

Here’s what I have tried so far:

1. Created a custom login view with:

   • Username and password input fields

   • A login button

   • Script on the login button using:

system.perspective.login(username=username, password=password)

2. Expected behavior:

   • When launching the Perspective session, my custom login view should appear instead of the default login page.

   • On clicking the login button, the credentials should validate against my configured usersource.

3. What actually happens:

   • No matter what I do, the default Perspective login page always appears first.

   • When I try system.perspective.login() from my view, it does not validate the username/password.

   • Instead, the session immediately redirects to the default login page, bypassing my view.

4. Observations / Possible causes:

   • I suspect system.perspective.login() only works within a session that allows login.

My main question:

• What is the recommended approach in Ignition 8.1 to use a completely custom login view instead of the default Perspective login page?

• Are there any other approaches to bypass the default login screen?

Thanks in advance for your guidance!

[pturmel]

Don't do this. Instead, find an Identity Provider that offers a suitable login page and use that. (You can create your own, as the protocols are standards, if you must.)