* If silentlogin do implicitLogin * If silentlogin do implicitLogin * Unit tests * Unit tests Trigger new run * Authguard should return true for canActive * adjust unit test and allow AuthGuard CanActive for the SSO case * adjust unit test and allow AuthGuard CanActive for the SSO case * adjust unit test and allow AuthGuard CanActive for the SSO case * adjust unit test and allow AuthGuard CanActive for the SSO case * Add isPublicUrl logic to authguard * adjust unit test and allow AuthGuard CanActive for the SSO case * Allow canActive true for public urls like /settings * fix redirect login for SSO * Try not using isPublicUrl from js-api as that triggers an implicit login already * Try not using isPublicUrl from js-api as that triggers an implicit login already * Try not using isPublicUrl from js-api as that triggers an implicit login already * Try not using isPublicUrl from js-api as that triggers an implicit login already * move sso silentlogin fix to ecm authguard * Try only todo the implicitLogin if not logged in * Try only todo the implicitLogin if not logged in * Try only todo the implicitLogin if not logged in * Try only todo the implicitLogin if not logged in * try figuring out why process cloud is failing * try figuring out why process cloud is failing * try figuring out why process cloud is failing * try figuring out why process cloud is failing * try figuring out why process cloud is failing * remove implicit flow parameter and pray that those process cloud tests are passing * remove implicit flow parameter and pray that those process cloud tests are passing * remove implicit flow parameter and pray that those process cloud tests are passing * try figuring out why process cloud is failing * try figuring out why process cloud is failing * try figuring out why process cloud is failing * try figuring out why process cloud is failing * try figuring out why process cloud is failing * try figuring out why process cloud is failing * try figuring out why process cloud is failing * try figuring out why process cloud is failing * move authService stuff in the login component from ngOnInit to constructor * move authService stuff in the login component from ngOnInit to constructor * move authService stuff in the login component from ngOnInit to constructor * move authService stuff in the login component from ngOnInit to constructor * not use login component for silent login anymore! * try figuring out why process cloud is failing * try figuring out why process cloud is failing * reuse is PublicUrl from js-api * reuse is PublicUrl from js-api * revert travis changes * revert travis changes * Check if oauth is enabled * Check if oauth is enabled * Check if oauth is enabled * Check if oauth is enabled
Alfresco Application Development Framework (ADF)
branch | status |
---|---|
master | |
development |
See the Introduction page to get started with the Alfresco Application Development Framework.
Prerequisites
Before you start using this development framework, make sure you have installed all required software and done all the necessary configuration. See our tutorial Preparing the development environment for full details.
Components
You can find the sources for all ADF components in the
lib
folder.
Full documentation for all components is available at the ADF Component Catalog.
Demo Application
A separate application showcasing integration of components can be found here. The app has examples of basic interaction for both APS and ACS components.
Yeoman generators
To speed up the development of your ADF application, use the Yeoman Generator. This will create a full working project with all the right libraries and tools.
Browser Support
All components are supported in the following browsers:
Browser | Version |
---|---|
Chrome | Latest |
Safari (OS X) | 9.x |
Firefox* | Latest |
Edge | 13, 14 |
Internet Explorer | 11 |
- Due to a known issue in Firefox, the Alfresco Upload Component does not currently support folder upload functionality on Firefox.
See the Browser Support article for more details.