Hello Sergei,
Apologies for the delay in response. We are working on the solution and will get back to you on soon.
Thank you, Anjali
Hi,
Yes, you can set the "ngModalOptions.backdrop" input of your modal to "static". I am attaching the screenshot of the code.
You can check the modal configurations from ng-bootstral documentation : https://ng-bootstrap.github.io/#/components/modal/examples#config https://ng-bootstrap.github.io/#/components/modal/api#NgbModalOptions
Hi
do you get this after login, can you share the steps to reproduce so we can reproduce this issue on our side? can you check result of endpoint /application-configuration and share the screenshot.
Hi,
Yo don't need to migrate from identity server but here is the link why to migrate if you need https://docs.abp.io/en/commercial/latest/migration-guides/openIddict-step-by-step Please go through the migration guide https://docs.abp.io/en/abp/latest/Migration-Guides/Index You can update your project step by step
And then follow this https://docs.abp.io/en/abp/latest/Themes/LeptonXLite/AspNetCore to migrate from lepton theme to lepton x
Please note in documentation it is lepton x lite but you can do the same for lepton x.(download a latest version commercial project and see the leptonx configurations in the projects)
Hi,
We have followed following steps:
create a app on okta (https://developer.okta.com/docs/guides/sign-into-web-app-redirect/asp-net-core-3/main/)
please add redirect url on okta of authserver (i see that you have added for angular this need to be authserver url)
and then install <PackageReference Include="Okta.AspNetCore" Version="4.5.0" /> package
add following config in appsetting.json
"Okta": { "OktaDomain": "https://dev-xxxxxxxx.okta.com", "ClientId": "0oaaxxxxxxxxxx", "ClientSecret": "VZlZPpOexxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "AuthorizationServerId": "default" }
let us know your email and we will share your this solution if possible.
Thanks, Anjali
Hi viswajwalith,
We are checking, will update you asap.
The id application generates the authorization code and then it is redirected to the client application. Where the code is used to generate access token and refresh token and other claims.
You can read more about authorization code flow here :
https://documentation.openiddict.com/guides/choosing-the-right-flow.html#authorization-code-flow-recommended-for-new-applicationson angular:
https://www.npmjs.com/package/angular-oauth2-oidchttps://github.com/abpframework/abp/blob/dev/npm/ng-packs/packages/oauth/src/lib/strategies/auth-flow-strategy.ts https://github.com/abpframework/abp/blob/dev/npm/ng-packs/packages/oauth/src/lib/strategies/auth-code-flow-strategy.ts#L35
The session details will be available on the client application after the user login. Please refer the attached screenshot where you can find the token details, after user login in my localhost. FYI,
You can read more about the abp claims in: https://docs.abp.io/en/abp/latest/Authorization#claims-principal-factory For getting the current user details on backend: https://docs.abp.io/en/abp/latest/CurrentUser The current user claims details: https://docs.abp.io/en/abp/latest/CurrentUser#icurrentprincipalaccessor
Hi,
We have update our answer with more information please do check again.
The id application generates the authorization code and then it is redirected to the client application. Where the code is used to generate access token and refresh token and other claims.
You can read more about authorization code flow here : https://documentation.openiddict.com/guides/choosing-the-right-flow.html#authorization-code-flow-recommended-for-new-applications
on angular: https://www.npmjs.com/package/angular-oauth2-oidc
https://github.com/abpframework/abp/blob/dev/npm/ng-packs/packages/oauth/src/lib/strategies/auth-flow-strategy.ts https://github.com/abpframework/abp/blob/dev/npm/ng-packs/packages/oauth/src/lib/strategies/auth-code-flow-strategy.ts#L35
The session details will be available on the client application after the user login. Please refer the attached screenshot where you can find the token details, after user login in my localhost. FYI, You can read more about the abp claims in: https://docs.abp.io/en/abp/latest/Authorization#claims-principal-factory For getting the current user details on backend: https://docs.abp.io/en/abp/latest/CurrentUser The current user claims details: https://docs.abp.io/en/abp/latest/CurrentUser#icurrentprincipalaccessor
Hello @phil@travelengine.com.au,
by default, the "TagViewComponent" widget comes with CMS Kit (namespace Volo.CmsKit.Public.Web.Pages.CmsKit.Shared.Components.Tags) and you can use it directly within your application. And the implementation for Blazor (Server/WASM) and MVC is mostly similar.
However, if you wish to implement it, I hope the following code would be useful.
[Widget(
StyleFiles = new[]
{
"/Pages/CmsKit/Shared/Components/Tags/default.css" // or the path that you want to use
})]
public class TagViewComponent : AbpViewComponent
{
protected readonly ITagAppService TagAppService;
public TagViewComponent(ITagAppService tagAppService)
{
TagAppService = tagAppService;
}
public virtual async Task<IViewComponentResult> InvokeAsync(
string entityType,
string entityId,
string urlFormat)
{
var tagDtos = await TagAppService.GetAllRelatedTagsAsync(entityType, entityId);
var viewModel = new TagViewModel
{
EntityId = entityId,
EntityType = entityType,
Tags = tagDtos,
UrlFormat = urlFormat
};
return View("~/Pages/CmsKit/Shared/Components/Tags/Default.cshtml", viewModel);
}
public class TagViewModel
{
public List<TagDto> Tags { get; set; }
public string EntityId { get; set; }
public string EntityType { get; set; }
public string UrlFormat { get; set; }
}
}
[Serializable]
public class TagDto : ExtensibleEntityDto<Guid>, IHasConcurrencyStamp
{
public string EntityType { get; set; }
public string Name { get; set; }
public string ConcurrencyStamp { get; set; }
}
Please let me know if this is what you are looking for.