Question Re: cds xsuaa suddenly requires using 'cds bind' and default-env.json no longer works in Technology Q&A

cds xsuaa suddenly requires using 'cds bind' and default-env.json no longer works

pieterjanssens — Thu, 28 Sep 2023 12:52:24 GMT

ERROR on server start: ❗️
Error: Authentication kind "xsuaa" configured, but no XSUAA instance bound to application. Either bind an IAS instance, or switch to an authentication kind that does not require a binding

I prefer using default-env.json as this allows me to swich cf cli sessions without affecting my developer workspaces...
This happend updating from 7.1.2 --> 7.2.1.

Re: cds xsuaa suddenly requires using 'cds bind' and default-env.json no longer works

Willem_Pardaens — Thu, 28 Sep 2023 13:22:14 GMT

The deprecation of default-env.json is mentioned here: https://cap.cloud.sap/docs/node.js/cds-env#in-default-env-json

Re: cds xsuaa suddenly requires using 'cds bind' and default-env.json no longer works

martinfrick — Thu, 28 Sep 2023 13:28:58 GMT

Hi piejanssens,

are you sure about that? Still works for me...

Martin

Re: cds xsuaa suddenly requires using 'cds bind' and default-env.json no longer works

pieterjanssens — Thu, 28 Sep 2023 13:35:54 GMT

Perhaps it's due to the way I'm defining/running my profile?

  "cds": {
    "requires": {
      "cds.xt.SaasProvisioningService": true,
      "[local]": {
        "cds.xt.SaasProvisioningService": false,
        "auth": {
          "kind": "xsuaa"
        }
      },
      "cds.xt.DeploymentService": false,
      "cds.xt.ModelProviderService": false,
      "uaa": {
        "kind": "xsuaa"
      },
...
}

Starting via "cds watch --profile local"

Re: cds xsuaa suddenly requires using 'cds bind' and default-env.json no longer works

pieterjanssens — Thu, 28 Sep 2023 15:05:39 GMT

Until it's officially unsupported, I'd like to keep using it. Even when it's deprecated.

Re: cds xsuaa suddenly requires using 'cds bind' and default-env.json no longer works

LuizGomes — Mon, 02 Sep 2024 18:39:06 GMT

I have the same problem in a Kyma instance, it loads the xusaa data but gives this error.