Console Login Widget Name

[Community Alums]

I want to edit the console login widget. If it's anything like the Portal process, I'm aware I'll need to clone it, make the changes I want, and then replace the default with my new widget. For the life of me, I cannot find the widget. 

Please note I am not referring to the SP 'Login' widget. I'm talking about the 'navpage.do' / 'console' default login page. 

I've looked through all the widgets under 'System UI > Widgets', and I've searched the 'System UI > UI Pages' but need help finding what I'm looking for. 

Is it locked down beyond regular Admin access?   Any assistance would be appreciated. 

Update: I'm using DOM as a workaround until I can find the widget. In a particular instance, we wanted our users to remember to log in with their admin credentials. For anyone interested, here is the code I'm using:

window.addEventListener(‘DOMContentLoaded’, function(){
	if (window.parent.document.location.pathname == ‘/navpage.do’) {
		
		// Change ‘User Name’ to ‘Admin user name’
		var element = window.parent.document.getElementsByClassName(“control-label”)[0];
		element.innerHTML = “Admin user name”;
		
		// Add placeholder username example
		window.parent.document.getElementById(‘user_name’).placeholder = “Inserted the format of our Admin user names”;
	}
});

[Soeren Maucher · Accepted solution]

Hello James, 

the "navpage.do" is a ui_page and as far as I know can not be customized. It does not use "widgets" as you know them from the portals. 
The only way I see how to achieve a highly customized login, would be to copy and customize a portal login page. Here you can change the style of the entire page as well as the login widget (widget-login). For example, change color, text layout. After successful authentication you can instantly redirect the user to the backend so he will never know he logged in via a portal page. 

I hope this helped. 

Greetings,
Sören

[Community Alums]

Thanks, Sören

I like your idea of using the portal login page and then redirecting to the console. I hadn't considered that.

I think for the time being, I'll stick with my DOM manipulation workaround. 

I appreciate the response.