Create a common layer for authentication & authorization component

[dhmlau]

Description / Steps to reproduce / Feature proposal

Capturing the information from @raymondfeng in today's meeting and in Slack.

We might need a common layer e.g. @loopback/security to serve as a base where @loopback/authentication and @loopback/authorization are two extensions. The common layer can possibly include:

• SecurityContext
• binding keys for current user/subject

From the conversation in Slack:

• Authentication binds the subject (who) to request context so that authorization can use it to make a decision against object + action (what)
• The subject contains a set of principals and other information from the access token (such as scopes)
• Today we build UserProfile, which is a subset of subject
• For example, facebook supports user token, client app token, page token etc
• The principal can a user, an application, or a device
• Maybe we should have a common module like @loopback/security to define the common interfaces/types

[dhmlau]

Draft PR #2902.
Recalling the conversation with @raymondfeng, he thinks after PR #1205 is done, we can see what makes sense to put in the common layer.

[jannyHou]

Closing as PR merged.