Confidential Docs
Authentication
Confidential Docs
Authentication
Search icon (depiction of a magnifying glass)
View GitHub RSS Feed
Set theme to dark (⇧+D)
  1. Products
  2. Authentication
  3. Implementation and notes

Implementation and notes

How to do this for existing routing components:

  1. Make sure you’re up-to-date with the generated code. So run the Angular Generator
  2. Make sure you’re up-to-date with the action list services. Run the Angular_ActionLoader generator
  3. Create an authorization service (if there isn’t one you can use)
  4. Update your route object in the *-routing.module.ts
  5. Update all *ngIfs

How to do this for new routing components:

  1. Make sure you’re up-to-date with the generated code. So run the Angular Generator
  2. Create an authorization service (if there isn’t one you can use)
  3. Create your route object in the *-routing.module.ts
  4. Create your routing component with all subcomponents (make sure to set all ngIfs)
  5. Run the Angular_ActionLoader generator

Notes:

*ngIf=“authorised” should not be removed yet, this will be done later on. Within entity pages the structure is as follows: detailpage (needs allowAction) detailtab (needs allowAction) detail (needs allowAction)

None of the abstract classes (entityDetailTabImplementationComponent for example) need allowAction, even though they currently have setFunctionsAndPermissions.