• if payment enabled for plan, provide widget to actually pay a bill (for consumers)
• handle trial period usage for stripe subscription
• provide payment information - get stripe information via API (for providers)
• provide bills as pdf -- basically a link to stripe (for consumers)
• email notification when a new bill is available with bill link (for consumers)

Some translation for Buttons are not applied :

use an actual payment service like stripe.

• setup stripe in tenant settings
• enabled paiement module in plan with a payment possibility
• handle plan type changes
• handle prices change (???)
• handle plan deletion => handle subscription deletion

Maybe with a chat component

When I delete a user by /settings/users/, there is no confirmation

this page/component must be used for tenant contact & team contact.
uber public accessibility of course.

• Create an UI to display all apikeys of an api
• Create an UI to manage apikey
  • update metadatas (cf #116 )
  • archive/delete apikeys

• link to a PDF file
• link to a website
• link to a zip file containing html
• link to a github project containing markdown
• link to a word file

• billing: use api and plan
• incomes: use team and plan

Create otoroshi services and groups for the current tenant. This should be a good way to implements multi-tenant for otoroshi

If I select a new avatar from an asset, nothing happens.

a starred api is necessarily in top of list
star an api is an action of user

maybe "tenant admin" can pin an important api for all users

It could be cool to add a wizard to initialize daikoku from a previous instance of Otoroshi.

• scan oto groups and suggest to create api (and team)
• scan apikeys to create DK subscriptions (and teams)

after validate the wizard, it will be necessary to update all api/plan/teams with non mondatory information (description, documentation...)

When I Create a new user, the "Set password" modal doesn't hide the information (type of input ...)

• users can create teams from frontend (My teams component)
• user who created team is admin of it
• admin can add members (like normal way)
• added members receive notification to accept addition
• users can accept or reject addition on team notification
• add this new way to add members on teams for admin team edit

• add it during apikey creation
• manage it during synchro job
  --> Daikoku holds the absolute truth, every token update will be overwrited

new metadata is "daikoku_integration_token"

Will allow to build public facing website to distribute API documentation and subscriptions

V1

• read only api to only get informations about apis
• fake subscription api (based on emailing)

V2

• identity api to create user and login
• subscription api
• apikeys management api

V3

• payment api

update plan to be able to select a particular service instead of a service group.

Tenant administrator have same level of permission of DaikokuAdmin but just for a tenant.
He can't manage users, tenants, session & import/export (all of Daikoku Administration part of back office).

• Generate automatic integration token foreach subscribtion
• Add an admin api to find subs by integration token
• Add new selector to choose integration type for plan (apikey or automatic -- add Private)
• Update UI with integration process: if apikey just token is display (except for admin)
• Update UI to hide private plans for another team than admin / update subscription process to use new plan subscription process and to protect private plans subscription
• move selector to choose subscription type to plan from api(manual or automatic)
• Hide apikey for all automatic integration subscription (admin can see the apikey)
• Generate events each time subscription/apikey is changed (creation, rotation disabling)
• Allow users to choose automatic integration for previous or non automatic integration apikey (in this case, regenerate secret after the choice)
• Update documentation

• if user.lastTenant is deleted, it's completly impossible to connect to DK ==> set to null user.lastTenant for all user after tenant deletion.
• team assets crash
• display more informations (No teams ?)

• Translation
  in http://.../bobbys-team/settings/apis/bobby-api-2/plans

• Translation

• swagger in API admin crash
  http://localhost:9000/evilcorpadminteam/settings/apis/adminapitenantdefault#

• subscription.rotation is null
  --> TeamApiKeysForApi.js:329

This job should gather information about billing periods of subcriptions and issue bills according to it

• run job with consumption job
• check end of payment period for each subscription with a thirdPartyPayment sub id
• send consumption information if needed & run bill creation
• send information to subscribers

In a long treatment, the end of user session coulb be shut down the work in progress...just because user has not be informed that his session will expire...

If I create a new User, I can click on "Create" again and again => "Conflict - The resource already exists"

Is it possible to redirect to the Users page after the creation or use the Toastr or change the Create btn as Save ... ?

An api to operate Daikoku, not UI oriented

• from JS frontend (should not be used)
• from JS backoffice (should use route id instead of object id)
• from JS adminbackoffice (should not be used)
• from controller actions
• from DB

With the help of a wizard, it could be nice to create all of work environements for an api

1. Inform How many environments to create
2. select otoroshi service group
3. for each env, associate it with a service (of the oto service group), and name the env to create the right plan (inform mandatory proporties for a new plan ex: type)
4. at the end, inform user that all oto service need the same exposed domain or we can give the url to oto
5. on save, all service in otoroshi are updated to accept one tag in...

this page present the same apis than home page...independently of the team selected

• New tab in api page to display a simple text for user information (realease for exemple)

• it would be good to inform all the teams that have subscribed to the API after a new post with a notification

• Add new option on plan to force secret auto-rotation for apikeys
• Add option on apikeys to choose secret auto-rotation
• Make the synchro between otoroshi and daikoku take into account apikey rotation (and change secret)
• update apikey by webhooks ?

• new tenant property style : page footer
• integrate it on all pages

• public access
• questions/answers system (like github)
• open/closed filter
• issue categorized with label
• notification after messages
• notification with links to issues/comments

When I want to create an account (/signup), you don't check if this is a real email, by example "titi" is accept :)

• Testin in Api resource

use api version to use same apikey for versioned service.

• account creation
• password forgotten
• user creation/update
• myProfile update
• team creation/update
• otoroshi settings creation/update
• tenant creation/update
• asset post (team & tenant)

When I click on "Remote content", all the content disappear

Provide a new view in main page to display API sorted by category

• add a way to customize category ?
• add a way to setup this display by default ?