shojy / webcore Goto Github PK

Support to be added to allow plugins to produce hooks, and consume those produced by other plugins.

The authentication provider should be extended to allow login via active directory account credentials. Account details should be cached and merged with the application, and the accounts should be linked into one.

Data on the user's name, email, and roles should be cached and integrated.

Hooks should be defined for almost every point in the application. These would include start and shutdown, requests, and others.

The core system should be able to discover and create Controllers and AppiControllers, and instantiate them with constructor injection where relevant

The authentication provider should be extended to allow users to login using social media accounts they link to their application account. (E.g. Facebook, Twitter, or Google account logins).

The application should link the social login to the account, and hand the actual login to the account provider using their respective APIs.

An authentication provider should be created to allow users to create and manage accounts, log in and out, allow for permissions to be set. Users should be stored within the application.

It would be nice to have a Single Sign On option for members of the Active Directory domain that made use of the Windows Authentication.

any documents for Core.Plugins.Api.Hooks.Communications and Core.Plugins.Api using?

An authentication filter that allows filtering by a user's name, role, resource, and intent should be created within the api library for plugins to use.

Plugins should have a method of deactivation without affecting the plugins files. Potentially a file located in the Plugins directory above each individual plugin that is checked on app start. A method of restarting the app may be required.

A default theme should be created for the theme support to fallback to.

Support for droppable and selectable "themes" should be added. This will allow a user to create a set of shared View files, and theme-specific bundle registrations. The selected theme should be searched first for any View pages required, followed by the default theme, and finally the built-in views for plugins and core.