Hi,
I'm sorry that I missguided you on this. You can create a domain service called UserService which implements IDomainService and move CreateOrUpdateUser from UserAppService to this new domain service. But if you do that, as I see from the code, you will need to move some other methods.
Maybe it's better to leave it this way in your case :)
Hi,
For the first question, you should create the user in ExternalLoginCallback in AccountController. User must be redirected to this action if any external authantication succeeds. Then you can create the user.
For the second question, first you need to authanticate and get a token in order to use it for the further requests. Please see this document <a class="postlink" href="https://www.aspnetzero.com/Documents/Development-Guide#token-based-authentication">https://www.aspnetzero.com/Documents/De ... entication</a>.
Hi,
Please see this forum topiv #1651@26063b0c-6028-4229-9744-2301f19ae305
Hi,
By defining a UserIdentifier like this
var userId = new UserIdentifier(null, AbpSession.UserId ?? 1);
you are pointing a user in host account by giving first parameter null to UserIdentifier.
If you disable MultiTenancy, then you should give tenantId to UserIdentifier.
var userId = new UserIdentifier(1, AbpSession.UserId ?? 1);
Even netter, you can use this.
var userId = AbpSession.ToUserIdentifier();
Hi,
Metronic has an example page what you are looking for. <a class="postlink" href="http://keenthemes.com/preview/metronic/theme/admin_4_material_design/ui_idle_timeout.html?p=page_user_lock_1">http://keenthemes.com/preview/metronic/ ... ser_lock_1</a>
This is the plugin used <a class="postlink" href="https://github.com/ehynds/jquery-idle-timeout">https://github.com/ehynds/jquery-idle-timeout</a>.
I haven't tried this but, I think you just need to call Account/Logout when this jquery plugin detects if user is idle for an amount of time.
No problem at all. Please let us know if you have any problems.
Hi,
You are doing it right. Please check this document for detailed information. if current unit of work is transactional, all changes in the transaction are rolled back if an exception occurs, even saved changes.
By the way, instead of calling another appService from PatientAppService, you can convert _iUserAppService to a DomainService and use it in your PatientAppService. <a class="postlink" href="http://aspnetboilerplate.com/Pages/Documents/Domain-Services">http://aspnetboilerplate.com/Pages/Docu ... n-Services</a>
Calling an AppService from another AppService is not considered as a good practice.
Hi,
Yes, please send to <a href="mailto:[email protected]">[email protected]</a>. Thanks.
Hi,
I couldn't find the problem on your files. Can you send your project via email ?
Hi,
For LDAP you dont have to create a user on your application. LDAP documentation is here <a class="postlink" href="http://aspnetboilerplate.com/Pages/Documents/Zero/User-Management#ldapactive-directory">http://aspnetboilerplate.com/Pages/Docu ... -directory</a>.
But if you are talking about ADFS, it's different than LDAP.