Highlighted
Not applicable

ATMOS CAS connection failed

Hi all,

I created a subtenant in my ATMOS device. It's working pretty fine while accessing it in REST (tried with both ATMOS Fox plugin and my applications).

Problem is that my applications have to access this subtenant in CAS. I generated a PEA File with the PEAGenerator found in your website, file looks totally OK (except for clusterid that i had to manualy get in an ATMOS XML configuration file). I had an error when trying to generate a connection pool.

I decided to try the pea with the JcenteraVerify tool, resulting with the following error : FP_AUTHENTICATION_FAILED_ERR    -10153

We already checked that every ATMOS Access Nodes are CAS enabled, we already try to generate new subtenant with their associated PEA files, resulting in the same error.

Any ideas ?

Thanks in advance.

Julien

0 Kudos
Reply
3 Replies
Highlighted
4 Beryllium

Re: ATMOS CAS connection failed

If you haven't already done so, open a ticket with EMC support.  You've already confirmed that the CAS service is enabled from the GUI, but you can doublecheck from the CLI with the command mauirexec 'service casd status'.

One possibility - formation of the Pool ID is pretty tricky.  It's a combination of the Subtenant ID and User ID (UID).  The ATMOS CAS Programmer's Guide shows you how to specify the Subtenant ID in a connection string - it's really easy to get the order wrong or use an illegal character.

Reply
Highlighted
Not applicable

Re: ATMOS CAS connection failed

Hi Karl,

Thanks for your answer. I'll ask Production Services to doublecheck with this CLI command.

As for the formation of the Pool ID, you are right, it's a combination of both values separated with a colon.

Here is an extract of the resulting PEA file

<pea version="1.0.0">

<defaultkey name="c6e52ed0b5ac4ebba24e7c5b4300ccc2:t00_sdt_dcs_dev_usr">

<credential id="csp1.secret" enc="base64">mysharedsecretencodedinbase64</credential>

</defaultkey>

<key type="cluster" id="52f9c3c4" name="c6e52ed0b5ac4ebba24e7c5b4300ccc2:t00_sdt_dcs_dev_usr">

<credential id="csp1.secret" enc="base64">mysharedsecretencodedinbase64</credential>

</key>

</pea>

0 Kudos
Reply
Highlighted
Not applicable

Re: ATMOS CAS connection failed

Hi again,

I asked Production to run the command on every Access Node, the result was the same on every host :

Checking for /opt/emc/casd/bin/casd: ..running

Nice try

0 Kudos
Reply