Used personnel user name and password [, which may get expired at some point in time [ based on the corporate policy ]] for pipeline to access the fdk-private-client-java v1.10.0-unreleased version

Fynd Platform FDK & API
#1

Hello Team,

At present, in jmshipmentfee extension, we hard-coded the value for user name and password to access the fdk-private-client-java v1.10.0-unreleased versionfor from pipeline, so that pipeline wont get into failure state.

This must be resolved, so that access to the fdk-private-client-java v1.10.0-unreleased versione from pipeline is standardised instead of using personnel, which may get expired at some point in time [ based on the corporate policy ].

#2

Hi @Pitchaimani

Here, we need to write a username and personal access token as a password to access the fdk-private-client-java. we do not need to write password here.

Personal access tokens have a maximum expiry of one year.

Furthermore, fdk-private-client-java is only for development and is provided as early access. You can use it on SIT or UAT environments. However, as it is highly unstable, you should not use it in a production environment. In a production environment, you should use the fdk-client-java public library available at GitHub - gofynd/fdk-client-java: Fynd Development Kit(FDK) for Java.

#3

@SoumyaAcharya - we are well aware of the usage of personnel access token usage in PROD environment. Please get in touch with @kedar2a to understand this particular use-case and try forward this request to engineering/devops team to come up with the solution for accessing fdk-private-client-java from prod pipeline.