Activities of "armanozak"

Hi alexander.nikonov,

The problem here was the use of extensible components even when the component was replaced. This is completely different from your issue. Please open a new question and we will do our best to help.

Hi @gvnuysal,

The code is generated correctly by the Suite and the behavior you see is normal.

e alone is not a number in JavaScript or the browser. Therefore, it is not a valid input all by itself. That doesn't mean you cannot use e in number inputs. For example, 125e-5 (or 1.25e-3) is a perfectly valid input.

Hi,

Yes, the Angular app is a single-page application. So, the web server that runs it should be configured to redirect all routes to the index.html file. Please read this section in our documentation and check the official Azure library for deployment.

Please let us know if this answers your question.

Hi,

Have you tried the setting I shared with you?

Hi tomasz.lewandowski@neuca.pl,

Yes, there is a bug, but it isn't because of the dot in the solution name. The proxy generator tries to resolve any types with the keyword "System" in it. It apparently cannot resolve the types properly when the solution name ends with the word "System" (and has a dot in the solution name). ~~We will fix it quickly.~~ ~~There is an open PR for this now.~~ Fixed.

Hi,

Changing only responseType won't work. Except for the project name and the issuer address, your oAuthConfig should look exactly like I shared.

Apart from that, your Angular app should have 2FA support at v3.2, but I don't know about backend. My colleague may help you with that.

Hi @dmeagor,

The apiName property in generated services are collected from the remoteServiceName property of each module in the /api/abp/api-definition response. The response looks like this:

{
  "modules": {
    "identityServer": {
      "rootPath": "identityServer",
      "remoteServiceName": "AbpIdentityServer",
      "controllers": { /* controller definitions here */ },
    },
    "types": { /* type definitions here */ }
}

The --api-name parameter, on the other hand, points to the setting in the environment.ts file we should use to fetch /api/abp/api-definition response from. This parameter is useful when building a module and is usually omitted or passed as default when developing apps.

One helpful tip: You can make the CLI ask you questions by running abp generate-proxy --prompt. It then explains what each parameter is good for.

Hi,

It is the default setting in application template as of v3.1 and, normally, you don't have to do anything about it. If the oAuthConfig option in your environment.ts looks similar to the following, that means you are using code flow.

import { Config } from '@abp/ng.core';

const baseUrl = 'http://localhost:4200';

export const environment = {
  /* other config removed for brevity */

  oAuthConfig: {
    issuer: 'https://localhost:44305',
    redirectUri: baseUrl,
    clientId: 'MyProjectName_App',
    responseType: 'code',
    scope: 'offline_access MyProjectName',
  },
 
  /* other config removed for brevity */
} as Config.Environment;

Hi,

For 2FA, code flow is required. When using code flow, your Angular application redirects the user to a login page made with MVC. This is why, customization of the login page must be done using MVC. Upgrading Angular to latest version will not change this.

How to customize that login page in MVC is out of my expertise, so I have assigned the question to a colleague who can answer that.

Hi,

You can use Angular for the rest of your app and implement 2FA. Only the login page will be MVC.