Documentation for edc.transfer.proxy.token... config is wrong

[florianrusch-zf]

The documentation at the following lines is wrong. There is no mechanism in place which will create random keys.

Connector/extensions/control-plane/transfer/transfer-data-plane/README.md

Lines 51 to 52 in 8193f3d

	| `edc.transfer.proxy.token.signer.privatekey.alias` | Alias of private key used for signing tokens | false | Random EC public key |
	| `edc.transfer.proxy.token.verifier.publickey.alias` | Alias of public key used for verifying the tokens | false | Random EC private key |

Proof:

Connector/extensions/control-plane/transfer/transfer-data-plane/src/main/java/org/eclipse/edc/connector/transfer/dataplane/TransferDataPlaneCoreExtension.java

Lines 113 to 122 in 8193f3d

	if (publicKeyAlias != null && privateKeyAlias != null) {
	var controller = new ConsumerPullTransferTokenValidationApiController(tokenValidationService, dataEncrypter, typeManager, (i) -> publicKeyService.resolveKey(publicKeyAlias));
	webService.registerResource(controlApiConfiguration.getContextAlias(), controller);
	var resolver = new ConsumerPullDataPlaneProxyResolver(dataEncrypter, typeManager, new JwtGenerationService(), getPrivateKeySupplier(context, privateKeyAlias), () -> publicKeyAlias, tokenExpirationDateFunction);
	dataFlowManager.register(new ConsumerPullTransferDataFlowController(selectorService, resolver));
	} else {
	context.getMonitor().info("One of these settings is not configured, so the connector won't be able to provide 'consumer-pull' transfers: [%s, %s]"
	.formatted(TOKEN_VERIFIER_PUBLIC_KEY_ALIAS, TOKEN_SIGNER_PRIVATE_KEY_ALIAS));
	}

[ndr-brt]

documenting the settings in a readme is highly discouraged because they get outdated easily, better to properly annotate the setting with the @Setting annotation so the documentation can be generated with the autodoc plugin

[github-actions]

This issue is stale because it has been open for 14 days with no activity.

[ndr-brt]

the documentation is being posted on gh pages, this is the current one:
https://eclipse-edc.github.io/Connector/autodoc/0.5.2-SNAPSHOT/

[segoranov]

documenting the settings in a readme is highly discouraged because they get outdated easily, better to properly annotate the setting with the @Setting annotation so the documentation can be generated with the autodoc plugin

already outdated, apart from the inconsistency mentioned in the issue, there is also no such parameter used at all: edc.transfer.client.selector.strategy (it's in the readme file only).

can i take this issue?