A violation against the OSS Rules of Play has been detected.

Rule ID: rl-assigned_teams-5
Explanation: Does teams have enough members on GitHub? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-reuse_tool-3
Explanation: Is it registered in REUSE? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-assigned_teams-1
Explanation: Does it have enough teams on GitHub? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-assigned_teams-2
Explanation: Does it have an admin team on GitHub? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-reuse_tool-1
Explanation: Does README mention REUSE? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

I found an inconsistency with the placeholder for the backend app URL in the SAAS Registry section of the download/installation instructions.

For example, the SAAS registry config file contains a placeholder <Your back-end app URL> to indicate the onSubscription URL. The example of what that would look like points to the inventorymanagementbackend app"

https://github.com/SAP/cloud-cf-multitenant-Inventory-management/blob/4fc53d1d2b3253245cd6b1b6e071409dccb6d0ae/Download_and_Installation_Instructions.md#L97-L101

Yet later on when providing details on what URL should be returned by the onboarding service, the same placeholder <Your back-end app URL> is used but this time the inventorymanagementui app is referenced

https://github.com/SAP/cloud-cf-multitenant-Inventory-management/blob/4fc53d1d2b3253245cd6b1b6e071409dccb6d0ae/Download_and_Installation_Instructions.md#L116-L120

So what we're seeing is that in one context, <Your back-end app URL> corresponds to inventorymanagementbackend while in another it corresponds to inventorymanagementui. Can this be revised to make it more clear which one is actually the backend app?

The OSPO bot created this issue by mistake - It did not have enough priviledge to check the vulnerability alerts, So I am closing this issue now. Sorry for any inconvenience.

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-assigned_teams-3
Explanation: Does it have enough admins on GitHub? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-reuse_tool-4
Explanation: Is it compliant with REUSE rules? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

I am trying to do a multi-tenant sample proof of concept in SAP Cloud Platform(SCP) using this repository as a reference.
I have encountered a couple of problems and I am not sure what is the problem here.
After deploying the application in subaccount1(space: APS), I went ahead and subscribed the deployed application from subaccount2. I see that the deployed application URL is not working.
It says the subaccount does not map to a valid identity zone. Screenshot attached.

Also, If I access the subaccount2's URL, I get a login screen, but after login, I am getting the following error.:
Internal Server Error
in login/callback REST call

Here is mta.yaml

`ID: attempt3
_schema-version: '2.1'
version: 0.0.1

modules:

• name: db3
  type: hdb
  path: db3
  parameters:
  memory: 256M
  disk-quota: 256M
  requires:

  • name: hdi_db3

• name: invbackend
  type: nodejs
  path: invbackend
  parameters:
  disk-quota: 1024M
  memory: 1024M
  provides:

  • name: invbackend_api
    properties:
    url: '${default-url}'
    requires:
    • name: hdi_db3
    • name: uaa_attempt3
      properties:
      SAP_JWT_TRUST_ACL:
    • clientid: ""
      identityzone: ""

• name: invui
  type: html5
  path: invui
  parameters:
  disk-quota: 256M
  memory: 256M
  build-parameters:
  builder: grunt
  requires:

  • name: uaa_attempt3
  • name: invbackend_api
    group: destinations
    properties:
    name: invbackend_api
    url: '~{url}'
    forwardAuthToken: true
    properties:
    TENANT_HOST_PATTERN: "^(.*)-invui.cfapps.eu10.hana.ondemand.com"

resources:

• name: hdi_db3
  parameters:
  config:
  database_id: [id placeholder]
  properties:
  hdi-container-name: ${service-name}
  type: com.sap.xs.hdi-container

• name: uaa_attempt3
  parameters:
  path: ./xs-security.json
  service-plan: application
  service: xsuaa
  shared: true
  type: org.cloudfoundry.managed-service

Here is the config.json{
"appId": "attempt3!t9256",
"displayName": "Inventory Management HANA App",
"description": "An app to manage your inventory which uses HANA DB with Column Discrimination",
"category": "Provider XYZ",
"appUrls": {
"onSubscription": "https://-invbackend./callback/v1.0/tenants/{tenantId}"
}
}`

Here is the xs-security.json
{ "xsappname": "attempt3", "tenant-mode": "shared", "description": "Security profile of called application", "scopes": [{ "name": "$XSAPPNAME.Callback", "description": "With this scope set, the callbacks for tenant onboarding, offboarding and getDependencies can be called.", "grant-as-authority-to-apps": [ "$XSAPPNAME(application,sap-provisioning,tenant-onboarding)" ] }] }

Please note that if I make the tenant-mode as dedicated, I am able to log in through provider URL.
Let me know if anything else is required.
TIA