Let's support authorization from github as it's done in Artipie.

Now all the possible errors while working with dashboard are displayed in the browser as simple text: json object with error description or exception stack trace. Let's process all the errors properly by showing them on the pages in human-readable format.

Let's support auth from environment as Artipie itself does. Variables for username and password are ARTIPIE_USER_NAME, ARTIPIE_USER_PASS.

Part of: #101

"Delete" button on the page to create repository looks confusing: repository in not yet created, thus there is nothing to delete. I'd suggest to rename it to "cancel"; this "cancel" button should simply redirect to the main user page with repositories list and discard all the changes.

Design authentication and authorization mechanisms for front service with backward compatibility of current Artipie implementation.

Dep: #3

Parse Artipie YAML configuration file from /etc/artipie/artipie.yml and create Storage instance based on these files (maybe create BlockingStorage instead of Storage).

Provide dashboard's interaction with Artipie only through exposed Artipie's rest api.

Sub-tasks:

• Singn in and obtaining JWT-token
• View repositories list
• Repository add
• Repository update
• Repository move
• Repository remove
• Correct readme for this repository and front service description to Artipie wiki

Let's add "cancel" button to dashboard page to edit repository. The button should simply return to the main page.

I am not a Java programmer, and just want to get/try the front end to Artipie.

Can you pleasde add a short "Getting Started" guide that outlines how to build / deploy (ideally containerised)

After more time than it should have taken I was able to build the project (mvn package) but now I have a jar file, it is not clear to me how to deploy - what is the container/web server etc?

Many Thanks

Docker passes port argument as --port=8080 to main, now it's not read in main. Let's parse this value from command line arguments and use as service port in Service.start() method.

Part of: #101
Provide following frontend UI to get repository setting control over REST API:

1. View list of repositories
2. add new repository configuration
3. update repository repository configuration
4. remove repository configuration

Remove maven-group repository and add docker-proxy. Also, removed old permissions from configs.

Artipie supports Keycloak authentication. However, there is currently no support to re-use existing Keycloak logins. This leads to users having to login again specifically for the Artipie dashboard.

In my use case, I have a reverse proxy that handles authorization with my Keycloak instance. So, when users reach the Artipie frontend, they are in fact already authenticated with Keycloak.

Within my reverse proxy, I have the user information and the token readily available. What would be ideal if if I can pass the token from Keycloak directly to the artipie frontend, where Artipie can directly authenticate the user with the token without having to show another login form.

I know this is probably quite some work. There are a number of other applications that already do this.

For example:
Fallenbagel/jellyseerr#184

I'm myself just an user of keycloak / openidc and I am trying to install SSO for the applications that I manage. I'm having trouble with Artipie. I just wanted to let you know that this may be something you want to support in the future :)

If there is anything I can do to clarify or help let me know!

Create app stub with service, configure build and pipelines.

Ref: artipie/artipie#988
CC: @artipie/members

Move dashboard from https://github.com/artipie/management-api/ repo:

• Java classes https://github.com/artipie/management-api/tree/master/src/main/resources/dashboard
• Templates: https://github.com/artipie/management-api/tree/master/src/main/resources/dashboard

To com.artipie.front.dashboard package. Integrate template renderer https://sparkjava.com/documentation.html#views-and-templates

After user of authorized with github credentials and prefix github.com/, this prefix should not be used and username itself should be added to session attributes.

When you edit repository name on dashbord the symbol '-' disallowed now, for example 'docker-repo' is forbedden now.
Repository name should allow to enter name containing '-' symbol.

Let's add conan repository to dashboard: corresponding option in listbox and description.

Design public API for repositories, users, permissions and storage:

• /repositories/{name} - for repositories
• /users/{name} - for users
• /permissions/{name} - for permissions
• /storage/{name} - for storage

All APIs are REST APIs with standard resource semantic. Support GET, PUT, HEAD, DELETE methods, e.g.:

• GET /repositories - list all repositories
• GET /repositories/{name} - get repository details
• PUT /repositories/{name} - creates new repository from payload (if no conflicts)
• HEAD /repositories/{name} - check repository exist (200 or 404 status)
• DELETE /repositories/{name} - delete repository by name

Let's start with some core design of these APIs, and then we decompose it to smaller tasks.

Let's add integration tests for API endpoints, goals of these tests are:

• make sure API endpoints are available by correct paths
• permissions/auth works as expected

We need to implement some self-reloading cache for YamlCredentials: now credentials yaml file is read on app start and never reloaded again.