Not Exactly, basically we need to validate AccessToken and create a user claimns and send the user to login page. If needed we may add new controller in our Web/Auth server as well.
Hi,
I remember that native apps like android and ios apps don't have cookies, make a mobile login page to send a request to the token endpoint is a better way.
Hi @Liangshiwei, yes we are able to use the generate the token by calling token URL, but our main query is what is way to login into the application by passing generated token and avoid login challange during this process
we'll test and get back to you
Sure will be waiting for ur response.
Hi,
Somwhow we are able to get that issue fixed by changing the way of configuring the elsa. Thanks for the support.
private void ConfigureElsa(ServiceConfigurationContext context, IConfiguration configuration)
{
context.Services
.AddElsa(
elsa =>
{
elsa
.AddMongoDbStores(configuration, databaseName: "AppV3_Elsa", connectionStringName: "ElsaServiceMongoDb");
})
.AddEmailActivities(options => options.Bind(configuration.GetSection("Elsa:Smtp")))
.AddHttpActivities(options => options.Bind(configuration.GetSection("Elsa:Server")))
.AddTimerActivities(options => options.Bind(configuration.GetSection("Elsa:Timers")));
context.Services.AddElsaDashboard(options => options.Configure(x => x.ActivityDefinitions
.Add<WriteLine>()
.Add<ReadLine>()
.Add<ReceiveHttpRequest>()
.Add<SendHttpRequest>()
.Add<WriteHttpResponse>()
.Add<SetVariable>()
.Add<ForEach>()
));
context.Services.AddUserActivities();
context.Services.AddAssemblyOf<Elsa.Dashboard.Areas.Elsa.Controllers.HomeController>();
context.Services.AddAssemblyOf<Elsa.WorkflowDesigner.ViewComponents.WorkflowDesignerViewComponent>();
context.Services.AddAssemblyOf<Elsa.Dashboard.Areas.Elsa.Controllers.WorkflowDefinitionController>();
context.Services.AddAssemblyOf<Elsa.Dashboard.Areas.Elsa.Controllers.WorkflowInstanceController>();
context.Services.AddNotificationHandlers(typeof(LiquidConfigurationHandler));
//Disable antiforgery validation for elsa
Configure<AbpAntiForgeryOptions>(options =>
{
options.AutoValidateFilter = type =>
type.Assembly != typeof(Elsa.Dashboard.Areas.Elsa.Controllers.HomeController).Assembly;
options.AutoValidateFilter = type =>
type.Assembly != typeof(Elsa.WorkflowDesigner.ViewComponents.WorkflowDesignerViewComponent).Assembly;
options.AutoValidateFilter = type =>
type.Assembly != typeof(Elsa.Dashboard.Areas.Elsa.Controllers.WorkflowDefinitionController).Assembly;
options.AutoValidateFilter = type =>
type.Assembly != typeof(Elsa.Dashboard.Areas.Elsa.Controllers.WorkflowInstanceController).Assembly;
});
}
@yekalkan thanks
Also,
We'll consider to SweetAlert2 https://github.com/abpframework/abp/issues/9413
Yes really confusing which leads to loss of one support ticket, can we get it back?
hi
Now it is a normal input element, I don't know why you need to destroy and create it again.
Use
abp-data-datepicker="false"will ignoreabp.dom.initializers.initializeDatepickersmethod.
thanks mailing, what ever you said sounds correct but not sure why it is not considering the respective attribute to false, do u think any file need to be Included?
hi
You can add
abp-data-datepicker="false"toabp-inputto prevent the framework from changing it.Then you can full use jquery to control it.
<abp-input asp-for="Observation.ObservationDate" value="@DateTime.Now.ToString("yyyy-MM-dd")" type="date" abp-data-datepicker="false" />
@maliming: It didn't worked even if we add the abp-data-datepicker="false" to abp-input, not sure how it worked for you.
we managed this by destroying the datepicker object and recreating the same.
$('#Observation_ObservationDate').datepicker("destroy"); $('#Observation_ObservationDate').datepicker({ format: 'mm-dd-yyyy', endDate: '+0d', autoclose: true, todayHighlight: true, todayBtn: true, });
Hi, @viswajwalith
Yes we can have a remote metting. shiwei.liang@volosoft.com
@liangshiwei I already sent a meeting invite and I think that time not suits you. Please send the meeting invite based on ur availability.
I am not able to make screenshare sessions. Please try the solutions above and share the results via this platform.
We are still facing the issue of accessing the API's using Swagger client of InternalGateway and WebGateway. I have qigen all required permissions. Still getting the error "Auth ErrorTypeError: Failed to fetch"
I hope someone from support team to help us in access the API's from Swagger client of gateway Applications.
@liangshiwei let me know if u want to have a screen share