[jira] [Created] (MRM-1969) admin account locked on Archiva UI, unable to create a new user
Sadiq Mo created MRM-1969: - Summary: admin account locked on Archiva UI, unable to create a new user Key: MRM-1969 URL: https://issues.apache.org/jira/browse/MRM-1969 Project: Archiva Issue Type: Question Components: browser, Documentation, system, Users/Security, Web Interface Affects Versions: 2.2.0 Reporter: Sadiq Mo Priority: Critical Attachments: Error when trying to create a new user.JPG, No password to enter while creating a new user.JPG Admin account for Archiva has been locked out due to incorrect password attempts and I am unable to create another user account or reset the current password through UI as when I reset the password it says "password reset" is there a way to find out which email the new password is being sent to or reset the password from Archiva application on the server. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MRM-1967) Purge snapshot repository
[ https://issues.apache.org/jira/browse/MRM-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291780#comment-16291780 ] Martin Stockhammer commented on MRM-1967: - Thanks for the information. The listing is not of a classical SNAPSHOT artifact. Snapshot versions should have a version scheme like 10.3.2-20171115.205652-17. Is this one of the snapshot artifacts that should be deleted? Or is this a listing of a released version? Do you have a group set for the artifact? If possible, could you attach the pom-File to this issue? > Purge snapshot repository > - > > Key: MRM-1967 > URL: https://issues.apache.org/jira/browse/MRM-1967 > Project: Archiva > Issue Type: Bug > Components: repository scanning >Affects Versions: 2.2.3 >Reporter: Pascal Jacob >Assignee: Martin Stockhammer > Attachments: Screen Shot 2017-11-29 at 12.48.11.png, archiva.xml, > artifact-listing.txt > > > Hello, > I have a snapshot repository with following settings: > - cron = 0 0 * * * ? > - days older = 0 > - retention count = 1 > - snapshots = true > - scanned = true > - delete released snapshots = true > Artifact filetype = rar > Repository scanning consumers: > - repository-purge = true > But nothing is purged. Nothing is cleaned up. Not even when starting > directory indexing manually (UI). > Any ideas what could be wrong? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MRM-1969) admin account locked on Archiva UI, unable to create a new user
[ https://issues.apache.org/jira/browse/MRM-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292153#comment-16292153 ] Martin Stockhammer commented on MRM-1969: - Depends on your configuration. If you have a database as user repository defined, you can remove the admin user from the database table. This should trigger the "Create admin user" link. > admin account locked on Archiva UI, unable to create a new user > --- > > Key: MRM-1969 > URL: https://issues.apache.org/jira/browse/MRM-1969 > Project: Archiva > Issue Type: Question > Components: browser, Documentation, system, Users/Security, Web > Interface >Affects Versions: 2.2.0 >Reporter: Sadiq Mo >Priority: Critical > Attachments: Error when trying to create a new user.JPG, No password > to enter while creating a new user.JPG > > > Admin account for Archiva has been locked out due to incorrect password > attempts and I am unable to create another user account or reset the current > password through UI as when I reset the password it says "password reset" is > there a way to find out which email the new password is being sent to or > reset the password from Archiva application on the server. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MRM-1967) Purge snapshot repository
[ https://issues.apache.org/jira/browse/MRM-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pascal Jacob updated MRM-1967: -- Attachment: globis-solutions-10.3.12-1.pom.xml > Purge snapshot repository > - > > Key: MRM-1967 > URL: https://issues.apache.org/jira/browse/MRM-1967 > Project: Archiva > Issue Type: Bug > Components: repository scanning >Affects Versions: 2.2.3 >Reporter: Pascal Jacob >Assignee: Martin Stockhammer > Attachments: Screen Shot 2017-11-29 at 12.48.11.png, archiva.xml, > artifact-listing.txt, globis-solutions-10.3.12-1.pom.xml > > > Hello, > I have a snapshot repository with following settings: > - cron = 0 0 * * * ? > - days older = 0 > - retention count = 1 > - snapshots = true > - scanned = true > - delete released snapshots = true > Artifact filetype = rar > Repository scanning consumers: > - repository-purge = true > But nothing is purged. Nothing is cleaned up. Not even when starting > directory indexing manually (UI). > Any ideas what could be wrong? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MRM-1967) Purge snapshot repository
[
https://issues.apache.org/jira/browse/MRM-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292146#comment-16292146
]
Pascal Jacob commented on MRM-1967:
---
I think we are getting close now. Problem could be in de POM file. To be
honest, this is our first attempt using an artifact repository like Archiva. So
not all functions are 100% clear to us on how to use them.
We are using following Maven command from within Jenkins to upload the artifact:
{code:java}
mvn deploy:deploy-file -Dfile=globis-solutions.rar
-DpomFile=globis-solutions.xml -DrepositoryId=GO10
-Durl=http://192.168.73.235:8060/repository/GO10 -DupdateReleaseInfo=true
{code}
We have added the -DupdateReleaseInfo parameter, because without it, following
API call did not always return the latest version of an artifact:
{code:java}
http://192.168.73.235:8060/restServices/archivaServices/searchService/artifact?g=10.3.12=globis-solutions=LATEST=rar
{code}
I have also attached the POM file to the issue.
> Purge snapshot repository
> -
>
> Key: MRM-1967
> URL: https://issues.apache.org/jira/browse/MRM-1967
> Project: Archiva
> Issue Type: Bug
> Components: repository scanning
>Affects Versions: 2.2.3
>Reporter: Pascal Jacob
>Assignee: Martin Stockhammer
> Attachments: Screen Shot 2017-11-29 at 12.48.11.png, archiva.xml,
> artifact-listing.txt, globis-solutions-10.3.12-1.pom.xml
>
>
> Hello,
> I have a snapshot repository with following settings:
> - cron = 0 0 * * * ?
> - days older = 0
> - retention count = 1
> - snapshots = true
> - scanned = true
> - delete released snapshots = true
> Artifact filetype = rar
> Repository scanning consumers:
> - repository-purge = true
> But nothing is purged. Nothing is cleaned up. Not even when starting
> directory indexing manually (UI).
> Any ideas what could be wrong?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (MRM-1967) Purge snapshot repository
[ https://issues.apache.org/jira/browse/MRM-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pascal Jacob updated MRM-1967: -- Attachment: archiva.xml artifact-listing.txt > Purge snapshot repository > - > > Key: MRM-1967 > URL: https://issues.apache.org/jira/browse/MRM-1967 > Project: Archiva > Issue Type: Bug > Components: repository scanning >Affects Versions: 2.2.3 >Reporter: Pascal Jacob >Assignee: Martin Stockhammer > Attachments: Screen Shot 2017-11-29 at 12.48.11.png, archiva.xml, > artifact-listing.txt > > > Hello, > I have a snapshot repository with following settings: > - cron = 0 0 * * * ? > - days older = 0 > - retention count = 1 > - snapshots = true > - scanned = true > - delete released snapshots = true > Artifact filetype = rar > Repository scanning consumers: > - repository-purge = true > But nothing is purged. Nothing is cleaned up. Not even when starting > directory indexing manually (UI). > Any ideas what could be wrong? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MRM-1967) Purge snapshot repository
[ https://issues.apache.org/jira/browse/MRM-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290506#comment-16290506 ] Pascal Jacob commented on MRM-1967: --- Not sure what you mean with artifact listing, but I attached the file list of one artifact. Archiva.xml also included. I edited the archiva.xml myself to set the days older value to zero. I read here before it was a known issue. > Purge snapshot repository > - > > Key: MRM-1967 > URL: https://issues.apache.org/jira/browse/MRM-1967 > Project: Archiva > Issue Type: Bug > Components: repository scanning >Affects Versions: 2.2.3 >Reporter: Pascal Jacob >Assignee: Martin Stockhammer > Attachments: Screen Shot 2017-11-29 at 12.48.11.png, archiva.xml, > artifact-listing.txt > > > Hello, > I have a snapshot repository with following settings: > - cron = 0 0 * * * ? > - days older = 0 > - retention count = 1 > - snapshots = true > - scanned = true > - delete released snapshots = true > Artifact filetype = rar > Repository scanning consumers: > - repository-purge = true > But nothing is purged. Nothing is cleaned up. Not even when starting > directory indexing manually (UI). > Any ideas what could be wrong? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MRM-1967) Purge snapshot repository
[ https://issues.apache.org/jira/browse/MRM-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pascal Jacob updated MRM-1967: -- Attachment: (was: archiva.xml) > Purge snapshot repository > - > > Key: MRM-1967 > URL: https://issues.apache.org/jira/browse/MRM-1967 > Project: Archiva > Issue Type: Bug > Components: repository scanning >Affects Versions: 2.2.3 >Reporter: Pascal Jacob >Assignee: Martin Stockhammer > Attachments: Screen Shot 2017-11-29 at 12.48.11.png, > artifact-listing.txt > > > Hello, > I have a snapshot repository with following settings: > - cron = 0 0 * * * ? > - days older = 0 > - retention count = 1 > - snapshots = true > - scanned = true > - delete released snapshots = true > Artifact filetype = rar > Repository scanning consumers: > - repository-purge = true > But nothing is purged. Nothing is cleaned up. Not even when starting > directory indexing manually (UI). > Any ideas what could be wrong? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MRM-1967) Purge snapshot repository
[ https://issues.apache.org/jira/browse/MRM-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pascal Jacob updated MRM-1967: -- Attachment: archiva.xml > Purge snapshot repository > - > > Key: MRM-1967 > URL: https://issues.apache.org/jira/browse/MRM-1967 > Project: Archiva > Issue Type: Bug > Components: repository scanning >Affects Versions: 2.2.3 >Reporter: Pascal Jacob >Assignee: Martin Stockhammer > Attachments: Screen Shot 2017-11-29 at 12.48.11.png, archiva.xml, > artifact-listing.txt > > > Hello, > I have a snapshot repository with following settings: > - cron = 0 0 * * * ? > - days older = 0 > - retention count = 1 > - snapshots = true > - scanned = true > - delete released snapshots = true > Artifact filetype = rar > Repository scanning consumers: > - repository-purge = true > But nothing is purged. Nothing is cleaned up. Not even when starting > directory indexing manually (UI). > Any ideas what could be wrong? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
