Introduce security log.

[maliming]

How to write security logs.

You can inject and use ISecurityLogManager to write security logs. It will create a log object by default and fill in some common values, such as CreationTime, ClientIpAddress, BrowserInfo, current user/tenant, etc. Of course, you can override them.

await SecurityLogManager.SaveAsync(securityLog =>
{
	securityLog.Identity = "IdentityServer";
	securityLog.Action = "ResourceOwnerPassword";
});

The security log store is implemented in Identity module.

Configure AbpSecurityLogOptions to provide the application name for the log or disable this feature. enabed by default.

Configure<AbpSecurityLogOptions>(x =>
{
	x.ApplicationName = "AbpSecurityTest";
});

[hikalkan]

Shouldn't be vice verse? I mean a filled eventData.ClientId should override the securityLog.ClientId. What do you think?
I didn't think much, but it seems like that. If that's true, no problem.

[hikalkan]

This can also be a "non transactional" UOW since it contains only one insert. It will reduce the dedlock probability.

[maliming]

Begin(requiresNew: true) is extension method.

abp/framework/src/Volo.Abp.Uow/Volo/Abp/Uow/UnitOfWorkManagerExtensions.cs

Lines 10 to 16 in ae8095d

	public static IUnitOfWork Begin(
	[NotNull] this IUnitOfWorkManager unitOfWorkManager,
	bool requiresNew = false,
	bool isTransactional = false,
	IsolationLevel? isolationLevel = null,
	int? timeout = null)
	{

[hikalkan]

I accepted the PR. Added two notes, so you can check and fix theme if necessary.

But the essentional design question is that: Why we are using event bus to save a security log. We should be able to directly use the ISecurityLogManager. Using evenbus is not a good way if we can use direct method calls.
If you want to decouple something, you can simply create an interface and implement in the Identity module.

Please re-consider this design and drop using the event bus.

[maliming]

Open a new PR for the above comment. #4810