Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(admin-ui): uploaded assets are not stored on server locations #1895

Open
manojs1978 opened this issue Nov 21, 2024 · 1 comment
Open
Assignees
Labels
bug Something isn't working comp-admin-ui Component affected by issue or PR kind-bug Issue or PR is a bug in existing functionality

Comments

@manojs1978
Copy link
Contributor

Describe the bug
uploaded assets are not stored on server locations
To Reproduce
Steps to reproduce the behavior:
install jans/flex 1.1.6.nightly/ 5.1.6.nightly
check asset configuration is present for jar and jans-link service
upload jar file type of asset file
showing asset uploaded on screen but it is not stored at desired location
See error

Expected behavior
when any asset uploaded it should store at their desired location if configuration is present

Screenshots
If applicable, add screenshots to help explain your problem.
image
image

Desktop (please complete the following information):
OS: ubuntu 22
Browser [e.g. chrome, safari]
Version [e.g. 22]
-flex 5.1.6.nightly
-DB pgsql/mysql

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

@manojs1978 manojs1978 added the bug Something isn't working label Nov 21, 2024
@mo-auto mo-auto added comp-admin-ui Component affected by issue or PR kind-bug Issue or PR is a bug in existing functionality labels Nov 21, 2024
@mjatin-dev mjatin-dev self-assigned this Jan 8, 2025
@pujavs
Copy link
Contributor

pujavs commented Jan 24, 2025

Analysis: Asset mapping for jans-lock and jans-link in document on the basis of which mapping configuration was written seems incorrect.
Mapping for *.jar should be /opt/jans/jetty/jans-lock/custom/libs rather than /opt/jans/jetty/jans-lock/custom-libs
Have asked @yurem for review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working comp-admin-ui Component affected by issue or PR kind-bug Issue or PR is a bug in existing functionality
Projects
None yet
Development

No branches or pull requests

6 participants