The button to delete a client including all contracts should only be visible if you have the permission 'clientAdmin'.

Currently, only the role 'clientAdmin' is checked, but it is not checked if this role exists in the corresponding organization.

Acceptance criteria:

• Role check must be organization dependent
• Role check must be performed for each client individually

We need a workflow similar to the one in the main project.

This bug only affects the Developer Portal version 1

Loading the Swagger file via the 'Try API' button works fine.
But as soon as you trigger a browser reload (e.g. F5) you get a 404 error, because the swagger file cannot be loaded.
To get the Swagger file again you have to use the Try Api button from the API list.

Maybe this bug will not be fixed anymore, depending on when version 1 will be completely replaced.

Here an alternative Icon should be displayed.

Add pipeline/instructions to perform an apiman release.

I have setup the APIMan and DevPortal in a VM and exposed the ports so that I can access them from my browser using vm-IP:Port.
I have published an API publicly but I am unable to see the API in DevPortal. After logging the DevPortal I get the following CORS error.

I am attaching container logs for better understanding. Any leads would be helpful. Thanks :)

containerLogs.txt

At the moment if a plan has no (only one policy) the policies of the API itself are displayed in the Plan Card.

We should discuss if we display api policies at all or put them in a new section e.g. "global policies".

This is related to apiman/apiman#1555

If you create files with ng generate they do not contain the copyright.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update angular-cli monorepo to v13.3.11 (@angular-devkit/build-angular, @angular/cli)
• chore(deps): update dependency @types/d3-scale to v4.0.3
• chore(deps): update dependency @types/d3-selection to v3.0.5
• fix(deps): update dependency @swimlane/ngx-charts to v20.1.2
• fix(deps): update dependency io.apiman:apiman-portal to v3.1.0.rc2
• fix(deps): update dependency json5 to v2.2.3
• fix(deps): update dependency luxon to v2.5.2
• chore(deps): update dependency cypress to v10.11.0
• chore(deps): update dependency eslint to v8.36.0
• chore(deps): update dependency eslint-config-prettier to v8.7.0
• chore(deps): update dependency jasmine-core to v4.6.0
• chore(deps): update dependency prettier to v2.8.4
• chore(deps): update dependency stylelint to v14.16.1
• chore(deps): update node.js to v16.19.1 (node, @types/node)
• chore(deps): update typescript-eslint monorepo to v5.55.0 (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• fix(deps): update dependency rxjs to v7.8.0
• fix(deps): update dependency tslib to v2.5.0
• chore(deps): update angular-cli monorepo to v15 (major) (@angular-devkit/build-angular, @angular/cli)
• chore(deps): update dependency @types/node to v18
• chore(deps): update dependency cypress to v12
• chore(deps): update dependency stylelint to v15
• chore(deps): update dependency stylelint-config-standard-scss to v7
• chore(deps): update dependency typescript to v5
• chore(deps): update node.js to v19
• fix(deps): update angular monorepo to v15 (major) (@angular/animations, @angular/common, @angular/compiler, @angular/compiler-cli, @angular/core, @angular/forms, @angular/platform-browser, @angular/platform-browser-dynamic, @angular/router)
• fix(deps): update angularmaterial monorepo to v15 (major) (@angular/cdk, @angular/material)
• fix(deps): update dependency keycloak-angular to v13
• fix(deps): update dependency keycloak-js to v21
• fix(deps): update dependency luxon to v3 (luxon, @types/luxon)
• fix(deps): update dependency ngx-markdown to v15
• fix(deps): update dependency simplebar to v6
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency @braintree/sanitize-url to 6.0.1 [security]
• chore(deps): update dependency json5 [security]
• chore(deps): update dependency luxon to 2.5.2 [security]
• chore(deps): update dependency webpack to 5.76.0 [security]
• chore(deps): update dependency cypress-real-events to v1.7.6
• chore(deps): update dependency husky to v8.0.3
• chore(deps): update nginx docker tag to v1.23.3
• fix(deps): update angular monorepo (@angular/animations, @angular/common, @angular/compiler, @angular/compiler-cli, @angular/core, @angular/forms, @angular/platform-browser, @angular/platform-browser-dynamic, @angular/router, zone.js)
• chore(deps): update dependency typescript to v4.9.5
• fix(deps): update dependency material-icons to v1.13.2
• fix(deps): update dependency swagger-ui to v4.18.1
• chore(deps): update angular-eslint monorepo to v15 (major) (@angular-eslint/builder, @angular-eslint/eslint-plugin, @angular-eslint/eslint-plugin-template, @angular-eslint/schematics, @angular-eslint/template-parser)
• chore(deps): update dependency karma-jasmine-html-reporter to v2
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

An API try-out page should be implemented.
In the first step it will be Swagger UI, as soon as some time is left it should be made configurable so that other solutions like ReDoc can be integrated.

Allow users the fully customize the look and feel of developer portal

E.g.

• Angular Templates
• Html Templates

We should take a look at the devportal and decide which components should be lazy loaded (e.g. Swagger)

The redirect after login by clicking 'Sign Up' on an API details page does not work.

In this context all redirects after login should be checked again.

Acceptance criteria:

• The redirect after successful login should always lead to the corresponding page.

Current

We read the default language from the config which is applied then.

Idea

Read the language from browser and token and then fallback to default config.

Acceptance

The language should be fetched from the browser settings or the token.
If one of that fails we should fallback to the default from the config file if the language is not available.

Use Logger for Developer Portal instead of console.log calls for debug logging

We should change npm install to npm ci to build reproducible artifacts and docker images.

If we only import fonts from an online source there will be no icons displayed when you have no access to the Google servers.
We should download the font including the icons.

Fixed link to SwaggerUI must be removed.
Instead, the try-out page should be configurable in order to be able to integrate other solutions, e.g. ReDoc or RapiDoc

Currently, there is no way to delete a client.
We have to think about that after a user disables all of his APIs or if he wants to rename a shared organization.

Description

I have installed and working apiman manager 2.0.0.Final and apiman-gateway vert.x 2.0.0.Final. After login successfully to the the apiman developer portal, it shows the next toast notification:

Investigation

It makes a call to the apiman manager in the endpoint /apiman/developers which does not exist. Currently my apiman manager serves under /apimanui/api-manager. I did not see in the docs more information about this I don't know if it's a bug or not.
Thanks in advance

The Developer Portal should show some notification.
There could be notifications for:

• your API subscription is awaiting approval
• your API subscription is approved
• your API subscription was rejected
• someone invited you into an shared organization

Discussion about a complete page, an bell icon or the place to put this is still open.

Provide i18n file for Developer Portal

https://angular.io/guide/i18n

Current

You can delete/unsubscribe from an API only if the whole client(application) is deleted.

Expected

You can unsubscribe from a single API without deleting the whole client(application).

In reference to the loaded core component the hero must appear in different shapes (change height and text)

Problem description

It's somewhat unclear what is going on as the TH elements are merged together.

Acceptance criteria

• Organization and Client columns should be clearly separated
• Should hint to user that they should click table element to populate search/create box (HTML hover highlight + mouse hint + perhaps slight change of text)

Hi I am trying to setup APIMan developer portal. I have built the docker image and tried running that image
I am getting the following error in my console.

Any leads will be helpful.

• Setup eslint https://github.com/angular-eslint/angular-eslint
• Setup pipeline step

Note: tslint is deprecated

The Devportal should at least work good on tablets and smartphones.

At the moment only clients with the org permission clientEdit are shown.

Acceptance

Clients from organizations with the permission clientEdit and clientView have to show on the my application page.

Problem description

• Publish APIs to developer portal, but don't explicitly feature anything.
• Home/featured page is blank

Proposal

• When >0 featured APIs: show featured APIs only
• When 0 featured APIs: show first N APIs (let's say 5 or 10?)

Acceptance Criteria

• Home page should never be blank if there are some APIs with appropriate discoverability level
• When >0 featured APIs: show featured APIs only
• When 0 featured APIs: show first N APIs (let's say 5 or 10?)

• Integrate Keycloak
• Token refresh
• HttpInterceptor (we have to think about which routes need Bearer Tokens and which not)
• Roles / Permissions

@bekihm Was there a reason why you used the environment variables via injection instead of the environment import?
With the second way, there is no need to set the variables via the constructor. I tested this and the variable substitution still works.

I have a feature request.

We have a convention that related APIs have the same prefix and would like to open the Your APIs with a filter to only display the relevant APIs.
In my case something like ".../devportal/?filter=Trebeg / testTable-*" (values are not URL encoded).

Create and execute (on github ci) cypress UI tests for the developer portal.

Since we need to import configuration data which defines many different things such as the language, style, images, or texts we must provide the application with an APP_INITIALIZER. These initializers are the best practice to preload data before the application may render its contents. The initializer should be easily extendable. In the first iteration it will prepare the i18n handling via config-file.

The new developer portal endpoints for plans and policies provide all necessary information with one request.
However, the Developer Portal does not use all the data and makes several unnecessary requests to retrieve the data again.

It should be adjusted so that only the necessary requests are made and all available data is used.

We have to discuss if/how we provide a migration between the two versions.

Problem description

In the highlighted segments we only show a placeholder. Instead, we should still consider showing the technical aspects so that the user can understand what they need to do

For example, X-Api-Key: <Key generated on signup>

Acceptance criteria

• Provide example with placeholder where key would be

We should display the current status of an API version.
For this we could use different icons in different colors with a corresponding label.
Example:
Green tick with label of ' Live '.

The status should be displayed on the API card (home and marketplace) according to the latest version and on the API details the status for each version should be in the accordion header.

Currently our main module imports these:
[...] MatButtonModule, MatCardModule, MatGridListModule, MatStepperModule, MatExpansionModule, MatIconModule, MatListModule [...]

We should define a seperate MaterialModule which imports Material dependencies. After, we can import this MaterialModule from our Main Module

Benefit:
Slimmed Main Module -> Improves clarity

We need a view to create applications and also a way to select the application during the API sign-up process.
This is currently missing in the MVP.

Choose which i18n mechanism we'll use for portal v2 (e.g. inbuilt/recommended mechanism or some external library). Whatever is best practice.

If a PR gets opened, we should find a way to publish the test results in the PR comments.
See the discussion in #13

Because of the old import/export problem we did not have a swagger definition in all cases.
This is fixed since the latest version.
So we can remove the head requests and check directly on the property in the api version.

Acceptance

• Remove head requests from api defintion calls

At the moment the Developer Portal is limited what policies can be displayed.
Currently we can only display the Rate Limiting and Transfer Quota Policy.

We should introduce a small concept which policies are relevant and decide what policy information should be displayed.

If something goes terribly wrong we should redirect the user to an error page.

Acceptance

• 404 page if they enter some really strange url we can recover from or redirect to home in all cases
• error page with contact information for help

In the wireframes, API version selection is part of the API sign-up process.
For the API try-out pages to work, the API version selection must already be possible on the API details page.
Accordingly, a new selection during the sign up is no longer necessary and can be removed there.