Support for base profile about che-che4z-explorer-for-endevor

[zdmullen]

Hi Denis,

The new version of the endevor-for-zowe-cli plugin is compatible with base profiles, version 6.1.0.

Please give it a try!

Thanks,

Zach

[zdmullen]

One other note here, from Michal Vasak on the Endevor team:

I think the issue here may be a matter of profiles precedence - the base profile connection information is only used if the Endevor-specific profile has no credentials defined. Otherwise the Endevor profile takes precedence.

So if a customer was using Endevor profiles before, it may look like the SSO doesn't work even after installing the plugin version that supports it, until they remove all credentials (and possibly other connection details like host/port, I'm not sure about that now..)

[FALLAI-Denis]

Hi,

Since the installation of version 6.1.0, then 6.1.1, of the endevor-for-zowe-cli plugin, errors have occurred concerning the version of the API.

After research, it turns out that the default "base path" has changed between versions 5.x and 6.x of the plugin:

• 5.x: --bp EndevorService/rest
• 6.x: --bp EndevorService/api/v2

After correcting the base path:

[FALLAI-Denis]

package: @broadcom/endevor-for-zowe-cli
version: 6.1.4

Test with Base profile (user/password) and secure-credential-store "update" (crypted) : "zowe profiles validate endevor" failed on "Check if username and password is valid", "Error: Missing specification for credentials"

Test with Base profile (user/password) and secure-credential-store "revert" (plain text) : "zowe profiles validate endevor" failed on "Check if username and password is valid", "Error: Missing specification for credentials"

Test with Base profile (user/password) without secure-credential-store (uninstall) : "zowe profiles validate endevor" failed on "Check if username and password is valid", "Error: Missing specification for credentials"
--> in this use case, Explorer for Endevor ask for user and password, so it don't use Base profile....

[Alexandru-Dumitru]

Hello Denis,

Thanks for conducting these tests. I have a question though, where they done solely on Explorer for Endevor or on the Endevor CLI as well?
The reason is that Explorer for Endevor doesn't support Base profile OR secure credential store yet. Even if the CLI supports it today, we haven't had a chance to implement it at the Explorer level, but it's something that it's definitely on our roadmap.

[FALLAI-Denis]

hi @Alexandru-Dumitru

For each configuration:

1. test on the Zowe CLI and the command "zowe profiles validate endevor <profile_name>"
2. test on declaration of a filter in Explorer for Endevor

When the secure-credential-store plugin is installed, whether active or inactive, it seems to trigger an error in Endevor Web Services regarding the length of the user code (userid).

Unless there is an error during our tests, the Zowe CLI interface does not support, or does not fully support, the secure-credential-store plug-in, nor the Base Profiles.

I can redo the tests with another method to be specified.

[jellypuno]

@FALLAI-Denis This is already implemented in v0.12.1. Can you please check?

[re891055]

Closed as duplicate. Please see #40 in case of need.