# Login component Authenticates to Alfresco Content Services and Alfresco Process Services. ![Login component](docassets/images/custom-footer.png) ## Contents - [Basic usage](#basic-usage) - [Properties](#properties) - [Events](#events) - [Details](#details) - [Handling events](#handling-events) - [Change footer content](#change-footer-content) - [Change header content](#change-header-content) - [Extra content](#extra-content) - [Custom logo and background](#custom-logo-and-background) - [Customize Validation rules](#customize-validation-rules) - [Controlling form submit execution behaviour](#controlling-form-submit-execution-behaviour) ## Basic usage ```html ``` ### Properties | Name | Type | Default value | Description | | ---- | ---- | ------------- | ----------- | | showRememberMe | `boolean` | `true` | Should the `Remember me` checkbox be shown? | | showLoginActions | `boolean` | `true` | Should the extra actions (`Need Help`, `Register`, etc) be shown? | | needHelpLink | `string` | `''` | Sets the URL of the NEED HELP link in the footer. | | registerLink | `string` | `''` | Sets the URL of the REGISTER link in the footer. | | logoImageUrl | `string` | `'./assets/images/alfresco-logo.svg'` | Path to a custom logo image. | | backgroundImageUrl | `string` | `'./assets/images/background.svg'` | Path to a custom background image. | | copyrightText | `string` | `'\u00A9 2016 Alfresco Software, Inc. All Rights Reserved.'` | The copyright text below the login box. | | providers | `string` | | Possible valid values are ECM, BPM or ALL. By default, this component will log in only to ECM. If you want to log in in both systems then use ALL. | | fieldsValidation | `any` | | Custom validation rules for the login form. | | disableCsrf | `boolean` | | Prevents the CSRF Token from being submitted. Only valid for Alfresco Process Services. | | successRoute | `string` | `null` | Route to redirect to on successful login. | ### Events | Name | Type | Description | | ---- | ---- | ----------- | | success | `EventEmitter` | Emitted when the login is successful. | | error | `EventEmitter` | Emitted when the login fails. | | executeSubmit | `EventEmitter` | Emitted when the login form is submitted. | ## Details ### Handling events **app.component.html** ```html ``` **app.component.ts** ```ts export class AppComponent { mySuccessMethod($event) { console.log('Success Login EventEmitt called with: ' + $event.value); } myErrorMethod($event) { console.log('Error Login EventEmitt called with: ' + $event.value); } } ``` ### Change footer content ![Login with custom footer](docassets/images/custom-footer.png) You can replace the entire content in the footer of the login component with your custom content. ```html My custom HTML for the footer ` ``` ### Change header content ![Login with custom header](docassets/images/custom-header.png) You can replace the entire content in the header of the login component with your custom content. ```html My custom HTML for the header ` ``` ### Extra content You can put additional html content between `alfresco-login` tags to get it rendered as part of the login dialog. This becomes handy in case you need to extend it with custom input fields handled by your application or parent component: ```html
Your extra content
``` Here's an example of custom content: ![Login with custom content](docassets/images/login-extra-content.png) ### Custom logo and background It is possible changing logo and background images to custom values. ```html ``` Should give you something like the following: ![Login with custom logo and background](docassets/images/custom-login.png) Alternatively you can bind to your component properties and provide values dynamically if needed: ```html ``` ### Customize Validation rules If needed it is possible to customise the validation rules of the login form. You can add/modify the default rules of the login form. **MyCustomLogin.component.html** ```html ``` **MyCustomLogin.component.ts** ```ts export class MyCustomLogin { @ViewChild('alfrescologin') alfrescologin: any; customValidation: any; constructor(public router: Router) { this.customValidation = { username: ['', Validators.compose([Validators.required, Validators.minLength(8), Validators.maxLength(10)])], password: ['', Validators.required] }; } ngOnInit() { this.alfrescologin.addCustomValidationError('username', 'minlength', 'Username must be at least 8 characters.'); this.alfrescologin.addCustomValidationError('username', 'maxlength', 'Username must not be longer than 11 characters.'); } } ``` ### Controlling form submit execution behaviour If absolutely needed it is possible taking full control over form submit execution by means of `executeSubmit` event. This event is fired on form submit. You can prevent default behaviour by calling `event.preventDefault()`. This allows for example having custom form validation scenarios and/or additional validation summary presentation. Alternatively you may want just running additional code without suppressing default one. **MyCustomLogin.component.html** ```html ``` **MyCustomLogin.component.ts** ```ts export class MyCustomLogin { validateForm(event: any) { let values = event.values; // check if the username is in the blacklist if (values.controls['username'].value === 'invalidUsername') { this.alfrescologin.addCustomFormError('username', 'the username is in blacklist'); event.preventDefault(); } } } ``` **Please note that if `event.preventDefault()` is not called then default behaviour will also be executed after your custom code.** ## See Also - [Logout directive](logout.directive.md)