npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: @typescript-eslint/[email protected]
npm ERR! node_modules/@typescript-eslint/parser
npm ERR! dev @typescript-eslint/parser@"^5.11.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @typescript-eslint/parser@"^4.0.0" from @typescript-eslint/[email protected]
npm ERR! node_modules/@typescript-eslint/eslint-plugin
npm ERR! dev @typescript-eslint/eslint-plugin@"^4.31.2" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! C:\Users\samzh\AppData\Local\npm-cache_logs\2023-08-14T14_35_57_171Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\samzh\AppData\Local\npm-cache_logs\2023-08-14T14_35_57_171Z-debug-0.log

See: casdoor/casdoor-go-sdk@1fa3da2

Like: https://github.com/casbin/node-casbin

SDK implementation code:

  public async getToken(id: string) {
    if (!this.request) {
      throw new Error('request init failed')
    }

    return (await this.request.get('/get-token', {
      params: {
        id: `admin/${id}`,  // Should admin be a username?
      },
    })) as unknown as Promise<AxiosResponse<{ data: Token }>>
  }

The api requires the id to be in the format owner/name：

// GetToken
// @Title GetToken
// @Tag Token API
// @Description get token
// @Param   id     query    string  true        "The id ( owner/name ) of token"
// @Success 200 {object} object.Token The Response object
// @router /get-token [get]
func (c *ApiController) GetToken() {
	id := c.Input().Get("id")
	token, err := object.GetToken(id)
	if err != nil {
		c.ResponseError(err.Error())
		return
	}

	c.ResponseOk(token)
}

If I pass built-in/admin, the api will throw an exception. If I pass admin, I can't get any data. What am I supposed to do?

The Node.js SDK and its parameters are too old: https://github.com/casdoor/casdoor-nodejs-sdk#step1-init-sdk

We should sync with the Go SDK: https://github.com/casdoor/casdoor-go-sdk#step2-init-config

https://github.com/casdoor/casdoor-nodejs-sdk/runs/5095336365?check_suite_focus=true

exports.casdoorCallback = async function(req, res){
  var callbackUrl = new URL(`http://localhost:3000/${req.url}`);

  const authCfg = {
    issuer: config.casdoorAuthConfig.issuer,
    clientId: config.casdoorAuthConfig.clientId,
    clientSecret: config.casdoorAuthConfig.clientSecret,
  }
  
  const sdk = new SDK(authCfg)
  await sdk.init();

  const tokenSet = await sdk.callback({
    code: callbackUrl.searchParams.get('code'),
    state: callbackUrl.searchParams.get('state')
  })

  // const parseToken = sdk.parseJwtToken(tokenSet.access_token || '')

  // logger.info(parseToken)
  res.redirect('/')
}

This is the code which i wrote but on the block

const tokenSet = await sdk.callback({
    code: callbackUrl.searchParams.get('code'),
    state: callbackUrl.searchParams.get('state')
  })

It breaks and gives error

Started 2022-02-17T09:49:02.943Z GET /callback?code=345f7e569cd85f7eb2e4&state=forum ::1
node:internal/process/promises:265
            triggerUncaughtException(err, true /* fromPromise */);
            ^

[RequestError: connect ECONNREFUSED 127.0.0.1:443
  at ClientRequest.<anonymous> (/home/mayank/gsoc/nodeclub/node_modules/got/dist/source/core/index.js:962:111)
  at Object.onceWrapper (node:events:640:26)
  at ClientRequest.emit (node:events:532:35)
  at ClientRequest.origin.emit (/home/mayank/gsoc/nodeclub/node_modules/@szmarczak/http-timer/dist/source/index.js:43:20)
  at TLSSocket.socketErrorListener (node:_http_client:442:9)
  at TLSSocket.emit (node:events:520:28)
  at emitErrorNT (node:internal/streams/destroy:157:8)
  at emitErrorCloseNT (node:internal/streams/destroy:122:3)
  at processTicksAndRejections (node:internal/process/task_queues:83:21)
  at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16)
] {
  code: 'ECONNREFUSED',
  timings: {
    start: 1645091343044,
    socket: 1645091343047,
    lookup: 1645091343048,
    connect: undefined,
    secureConnect: undefined,
    upload: undefined,
    response: undefined,
    end: undefined,
    error: 1645091343051,
    abort: undefined,
    phases: {
      wait: 3,
      dns: 1,
      tcp: undefined,
      tls: undefined,
      request: undefined,
      firstByte: undefined,
      download: undefined,
      total: 7
    }
  }
}

Which i can't figure out why it is happening

https://github.com/casdoor/casdoor-nodejs-sdk/runs/5128321069?check_suite_focus=true

This PR: https://github.com/casdoor/casdoor-nodejs-sdk/pull/28/files was reverted.

We need to use the "partial class" way to support all APIs again

When I call sdk.getAuthToken(code) with Casdoor SaaS is always returning:

{
  "error": "unsupported_grant_type",
  "error_description": "grant_type:  is not supported in this application"
}

So I noticed is related to the Authorization headers, the SDK pass the client_id and client_secret as:
Authorization: Basic {base64}

But to work properly should pass as:
Authorization: Bearer Basic {base64}

We need a new release which contains PR: #19

I've following this example but when I change the serverUrl the request fail

app.post('*', (req, res) => {
  let urlObj = url.parse(req.url, true).query;
  sdk.getAuthToken(urlObj.code).then(response => {
    console.log(response)
    const accessToken = response.access_token;
    // const refresh_token = response.refresh_token;
    res.send(JSON.stringify({ token: accessToken }));
  });
});

https://github.com/casdoor/casdoor-nodejs-react-example/blob/b2293f0895a0e2817601faeafd593543d1c59314/backend/server.js#L88-L96

With the default application it is working fine (https://door.casdoor.com), however when I configure my server configuration, it still gives me the same error.

I think that behind the configuration, it never makes the request to the server, and it is always doing it to the casdoor url, as I put in the image
This is my server.js configuration

const authCfg = {
  endpoint: 'https://cas-door-api-g5262uil2a-uc.a.run.app',
  clientId: '7f527a08271d88e3aa80',
  clientSecret: 'ac042d287d923799441ab820327e30510c194be7',
  certificate: cert,
  orgName: 'acium-team',
  appName: 'application_5tusgq',

} and this is the settings.js configuration

  //serverUrl: "https://door.casdoor.com",
  serverUrl: 'https://cas-door-api-g5262uil2a-uc.a.run.app',
  clientId: "7f527a08271d88e3aa80",
  organizationName: "acium-team",
  appName: "application_5tusgq",
  /*clientId: "014ae4bd048734ca2dea",
  organizationName: "casbin",
  appName: "app-casnode",*/
  redirectPath: "/callback", // in accordance with casdoor configuration
};

_Originally posted by @ErnestoCamilo in https://github.com/casdoor/casdoor-nodejs-sdk/issues/40#issuecomment-1805775934_
            

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Like Go and Java: casdoor/casdoor-java-sdk#64

Here's an example commit (still has bugs left): 55e00ff

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

The group tree means this part: https://door.casdoor.com/trees/built-in

The group tree mainly relies on the data returned by the get-groups API. But the returned data is a list. The Casdoor frontend code will build the tree from the list. We may need to do so too. There are two ways:

1. Build the tree in Casdoor Go backend: https://github.com/casdoor/casdoor/blob/master/controllers/group.go#L31
2. Build the tree in the SDK (like this casdoor-java-sdk)

Refer to:

• Go: casdoor/casdoor-go-sdk#83
• Java: casdoor/casdoor-java-sdk#62
• Python: casdoor/casdoor-python-sdk#65

This issue tries to help the issue from Galoy: GaloyMoney/galoy#294

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: @typescript-eslint/[email protected]
npm ERR! node_modules/@typescript-eslint/parser
npm ERR! dev @typescript-eslint/parser@"^5.11.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @typescript-eslint/parser@"^4.0.0" from @typescript-eslint/[email protected]
npm ERR! node_modules/@typescript-eslint/eslint-plugin
npm ERR! dev @typescript-eslint/eslint-plugin@"^4.31.2" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! C:\Users\samzh\AppData\Local\npm-cache_logs\2023-08-14T13_26_36_992Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\samzh\AppData\Local\npm-cache_logs\2023-08-14T13_26_36_992Z-debug-0.log

The author for PR: #4 is not active any more. We want to integrate his code with another PR.

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀