extensions.typo3.org issueshttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues2022-11-18T12:47:19Zhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/491Token ID list2022-11-18T12:47:19ZgilbertsoftToken ID list### Problem to solve
Currently a token disapears after the creation and the users have no idea about the created tokens and the assigned rights and extensions.
### Further details
<!--- Include use cases, benefits, and/or goals (contr...### Problem to solve
Currently a token disapears after the creation and the users have no idea about the created tokens and the assigned rights and extensions.
### Further details
<!--- Include use cases, benefits, and/or goals (contributes to our vision?) -->
### Proposal
It would be great to have an overview of the created tokens (names) and the assigned rights and extensios. Also a button to revoke a token would be great.
### What does success look like, and how can we measure that?
<!--- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this -->
Example from Github Secrets:
![image](/uploads/ffa0189d03559fef00e948880e8f8c29/image.png)
**Acceptence Criterias**
* [ ] simple list of token names
* [ ] optional, the assigned rights and extensions
* [ ] optional, a revoke button
### Links / referencesBacklogBenni MackOliver BartschBenni Mackhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/525Email notification on token expiration2022-04-04T17:31:04ZRudy GnoddeEmail notification on token expiration### Problem to solve
Access tokens expire after at most a year. It would be handy if there was an email notification when a token is about to expire, so users can update them.
### What does success look like, and how can we measure tha...### Problem to solve
Access tokens expire after at most a year. It would be handy if there was an email notification when a token is about to expire, so users can update them.
### What does success look like, and how can we measure that?
**Acceptence Criterias**
* [ ] Email notification when token is about to expire
* [ ] Email notification when token has expiredBackloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/548TER REST API throws exception on TYPO3 version although the version is given2022-05-15T19:23:44ZChristian BuelterTER REST API throws exception on TYPO3 version although the version is givenWhen uploading the Extension "access_keys" via tailor the API throws an exception that no full version for TYPO3 Core is given although a version is given.
Uploading manually into the TER works.
## Exception
```
array (
0 => '{"stat...When uploading the Extension "access_keys" via tailor the API throws an exception that no full version for TYPO3 Core is given although a version is given.
Uploading manually into the TER works.
## Exception
```
array (
0 => '{"status":400,"code":1604923182,"error":"invalid_request","error_description":"No full version for TYPO3 Core given."}',
)
```
The exeception seems to be generated here:
https://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/blob/develop/extensions/ter_rest/Classes/Service/Extension/VersionService.php#L313
## em_conf.php
The full `em_conf.php` is:
https://gitlab.com/codingms/typo3-public/access_keys/-/blob/main/ext_emconf.php
```
<?php
$EM_CONF['access_keys'] = [
'title' => 'Access-Keys for Backend',
'description' => '',
'category' => 'backend',
'author' => 'Thomas Deuling',
'author_email' => 'typo3@coding.ms',
'state' => 'alpha',
'internal' => '',
'uploadfolder' => '0',
'createDirs' => '',
'clearCacheOnLoad' => 0,
'version' => '1.0.1',
'constraints' => [
'depends' => [
'typo3' => '10.4.0-11.5.99',
],
'conflicts' => [
],
'suggests' => [
],
],
];
```BacklogOliver BartschOliver Bartschhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/554Question: REST API - query extensions2022-05-17T17:12:15ZOliver HaderQuestion: REST API - query extensions```
GET /api/v1/extension?page=1&per_page=50&filter%5Btypo3_version%5D=10
```
I was using above endpoint and foundation in order to fetch all extensions that
* are at least compatible with TYPO3 v10 (`typo3_version>=10`)
* that referen...```
GET /api/v1/extension?page=1&per_page=50&filter%5Btypo3_version%5D=10
```
I was using above endpoint and foundation in order to fetch all extensions that
* are at least compatible with TYPO3 v10 (`typo3_version>=10`)
* that reference to a composer name (`meta/composer_name<>''`)
Thanks in advance for any feedback, how to retrieve that data.BacklogOliver BartschOliver Bartschhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/586Outdated extension metadata from TER REST API2023-08-15T19:28:29ZElias HäußlerOutdated extension metadata from TER REST API### Summary
When requesting extension metadata through TER REST API, the responded information is not always correct. For example, the latest version of EXT:news supports TYPO3 v11 and v12, whereas the API response shows that only TYPO3...### Summary
When requesting extension metadata through TER REST API, the responded information is not always correct. For example, the latest version of EXT:news supports TYPO3 v11 and v12, whereas the API response shows that only TYPO3 v11 is supported.
### Steps to reproduce
Perform request to https://extensions.typo3.org/api/v1/extension/news and compare the response with extension metadata shown at https://extensions.typo3.org/extension/news.
### Example URL
See above.
### What is the current *bug* behavior?
Extension metadata is incorrect – the shown TYPO3 versions do not include all actually supported TYPO3 versions of the latest available version.
### What is the expected *correct* behavior?
The API response should include all actually supported TYPO3 versions.
### Relevant logs and/or screenshots
Current API response:
```json
[
{
"key": "news",
"downloads": 1747634,
"verified": true,
"version_count": 80,
"meta": {
"packagist": "https://packagist.org/packages/georgringer/news",
"composer_name": "georgringer/news",
"forge_link": "https://github.com/georgringer/news",
"repository_url": "https://github.com/georgringer/news",
"external_manual": "",
"paypal_url": "https://www.paypal.me/GeorgRinger/25",
"tags": [
{
"title": "News"
},
{
"title": "Extbase"
},
{
"title": "Fluid"
},
{
"title": "tags"
},
{
"title": "categories"
},
{
"title": "article"
},
{
"title": "Bestpractice"
},
{
"title": "responsive"
},
{
"title": "best-practice"
},
{
"title": "extension"
},
{
"title": "tx-news"
}
]
},
"current_version": {
"title": "News system",
"description": "Versatile news system based on Extbase \u0026 Fluid and using the latest technologies provided by TYPO3 CMS.",
"number": "11.0.0",
"state": "stable",
"category": "fe",
"typo3_versions": [
11
],
"dependencies": {
"typo3": "11.5.19 - 12.9.99",
"php": "7.4.0 - 8.2.99"
},
"conflicts": [],
"downloads": 0,
"upload_date": 1678361701,
"review_state": 0,
"download": {
"composer": "composer req georgringer/news",
"zip": "https://extensions.typo3.org/extension/download/news/11.0.0/zip",
"t3x": "https://extensions.typo3.org/extension/download/news/11.0.0/t3x"
},
"author": {
"name": "Georg Ringer",
"email": "mail@ringer.it",
"company": ""
}
}
}
]
```_Ready for sprinthttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/587Error 403 when trying to refresh access token via REST API2023-08-15T19:26:28ZElias HäußlerError 403 when trying to refresh access token via REST API### Summary
I try to refresh an access token via TER REST API. The access token was generated with permissions `extension:read` and `extension:write`. All other endpoints work smoothly, but when requesting `/auth/token/refresh`, I keep ...### Summary
I try to refresh an access token via TER REST API. The access token was generated with permissions `extension:read` and `extension:write`. All other endpoints work smoothly, but when requesting `/auth/token/refresh`, I keep getting a 403 response.
Side note: I am able to refresh the exact same token via TER UI at https://extensions.typo3.org/my-access-tokens/refresh.
### Steps to reproduce
1. Create access token with permissions `extension:read` and `extension:write`
2. Try to refresh access token via TER REST API (see curl example below)
### Example URL
Example request:
```bash
curl -X POST https://extensions.typo3.org/api/v1/auth/token/refresh -H "Authorization: Bearer xxx" -d "token=yyy"
```
### What is the current *bug* behavior?
Error 403 response, token is not refreshed.
### What is the expected *correct* behavior?
201 response as written in the [API specification](https://extensions.typo3.org/faq/rest-api#/Auth/refreshToken).
### Relevant logs and/or screenshots
API response:
```
{"status":403,"code":1602754893,"error":"access_denied","error_description":"The user lacks necessary permissions for this endpoint."}
```