AnsweredAssumed Answered

Aveksa Web Service command CreateChangeRequest

Question asked by Lakshman Varadharajan on Sep 11, 2015
Latest reply on Mar 30, 2017 by Alex Tetreault

Like • Show 0 Likes0
Comment • 10

I wanted to use the Aveksa Webservice to create Change Request using Webservcie, But I don't know how to send the Input parameter.I don't know what i am doing wrong here..

I am trying with Chrome extension "Advance REST client" to test it.

POST URL

http://172.31.xx.xx:8080/aveksa/command.submit?cmd=createChangeRequest

Payload

<Operation>Delete</Operation>

<BusinessSource>Credit Application</BusinessSource>

</AccountChange>

for the above URL i am getting the below error ERROR :

401 The token is not valid for the command 'createChangeRequest'. Token parameter was not present

I know it is authorization error but not sure how to pass it as input parameter (username and password

So what should be the POST URL

http://172.31.240.178:8080/aveksa/command.submit?cmd=createChangeRequest&token=<?>

Any example on this would be greatly apprecitated

Boris Lekumovich

Sep 12, 2015 2:00 AM

Correct Answer

first, you need to send a loginUser, to get the token.

Here is an example:

Send a post request to: http://172.31.xx.xx:8080 /aveksa/command.submit?cmd=loginUser

<username>AveksaAdmin</username>
<password>AveksaPassword</password>

The response will look like this:

token=ws31990ea07fcd1e8896:51aa757c:14f368f147f:-71450.08224484800695109

Now, you can send your createChangeRequest to:

http://172.31.240.178:8080/aveksa/command.submit?cmd=createChangeRequest&token=ws31990ea07fcd1e8896:51aa757c:14f368f147f:-71450.08224484800695109

Here is an example to removing entitlement

<Changes>
   <Description>desc</Description>
   <Notes>notes</Notes>
   <AccountChange>
   <Operation>Remove</Operation>
   <Account>testaccount</Account>
   <AccountCollector>Payroll Account Collector</AccountCollector>
   <BusinessSource>Payroll</BusinessSource>
   <Resource>401k</Resource>
   <Action>Administrator</Action>
   </AccountChange>
</Changes>

See the reply in context

No one else had this question

Outcomes

Boris Lekumovich

Sep 12, 2015 2:00 AM

first, you need to send a loginUser, to get the token.

Here is an example:

Send a post request to: http://172.31.xx.xx:8080 /aveksa/command.submit?cmd=loginUser

<username>AveksaAdmin</username>
<password>AveksaPassword</password>

The response will look like this:

token=ws31990ea07fcd1e8896:51aa757c:14f368f147f:-71450.08224484800695109

Now, you can send your createChangeRequest to:

http://172.31.240.178:8080/aveksa/command.submit?cmd=createChangeRequest&token=ws31990ea07fcd1e8896:51aa757c:14f368f147f:-71450.08224484800695109

Here is an example to removing entitlement

<Changes>
   <Description>desc</Description>
   <Notes>notes</Notes>
   <AccountChange>
   <Operation>Remove</Operation>
   <Account>testaccount</Account>
   <AccountCollector>Payroll Account Collector</AccountCollector>
   <BusinessSource>Payroll</BusinessSource>
   <Resource>401k</Resource>
   <Action>Administrator</Action>
   </AccountChange>
</Changes>

Actions

Lakshman Varadharajan @ Boris Lekumovich on Sep 14, 2015 2:12 PM

Thank you BorisL,

It worked.

Then when i tried for Delete account it is throwing the below error.

412 The change request could not be created. Changes element could not be found. Query String=cmd=createChangeRequest&token=ws31aeb9bdb40ee71b3a:a877881:14fcccd3d12:-7d320.865717998328923

Below is the payload

	<AccountChange>
	<Operation>Delete</Operation>
	<User>user1</User>
	<BusinessSource>IAG Application</BusinessSource>
	</AccountChange>

Any idea why ?

Actions

Lakshman Varadharajan @ Lakshman Varadharajan on Sep 14, 2015 2:21 PM

I got it..

we need to send the payload as below

<Operation>Delete</Operation>

<AccountCollector>IAG Application Account</AccountCollector>

<BusinessSource>IAG Application</BusinessSource>

</AccountChange>

</Changes>

The documentation is misleading

Actions

Alex Tetreault @ Boris Lekumovich on Mar 30, 2017 12:02 PM

Hi,

We are trying to remove a local entitlement from a user but getting an error about the system not be able to find the user. If we try to remove the AD account for the same user, it works fine.

Here is the XML for removing the local entitlement:
<Changes>
<Description>Test</Description>
<Notes>Removing local entitlement</Notes>
<UserChange>
<Operation>Remove</Operation>
<User>akc1234</User>
<BusinessSource>Manual Tasks - L1</BusinessSource>
<Resource>RSA Admin</Resource>
<Action>RSA - Helpdesk</Action>
</UserChange>
</Changes>

This is the error we get:

The change request could not be created. Could not retrieve user from the id 'akc1234'. <?xml version="1.0"
encoding="UTF-8"?><UserChange> <Operation>Remove</Operation> <User>akc1234</User> <BusinessSource>Manual Tasks -
L1</BusinessSource> <Resource>RSA Admin</Resource> <Action>RSA - Helpdesk</Action> </UserChange> Query
String=cmd=createChangeRequest&token=ws31e08acc70b374b2db:7ba4cdf8:15b1f554598:25d90.5321081583431172
description A specified precondition has failed for this request (The change request could not be created. Could not retrieve
user from the id 'akc1234'. <?xml version="1.0" encoding="UTF-8"?><UserChange> <Operation>Remove</Operation>
<User>akc1234</User> <BusinessSource>Manual Tasks - L1</BusinessSource> <Resource>RSA Admin</Resource> <Action>RSA -
Helpdesk</Action> </UserChange>

Since we can delete or add accounts and other platform entitlements for the same user, we know the user does exist. I tried removing the entitlement from an account, but there really is no account for a local entitlement.

Thanks,

Alex

636-722-7684

Actions

Alex Tetreault Aug 12, 2016 4:09 PM

Hi,

In the example provided as the answer to the original question, what is the entitlement? 401k? Administrator? Without using the XML tag in the answer, what goes in the XML tags Resource and Action?

I'm trying to remove an Active Directory group and have tried both the 'Remove entitlement from user' and 'Remove entitlement from account' change request actions with different flavors of Resource and Action, but it keeps responding that 'the entitlement for resource and action can't be found for application. I know the group is there though because I can see it under the 'What Access' tab in the Directory.

It would be really helpful if there was better documentation for using the web services including examples of what the XML tags are mapped to.

Thanks,
Alex

Actions

Boris Lekumovich

@ Alex Tetreault on Aug 14, 2016 1:59 AM

Alex, try using "Remove account from group" capability

Actions

Alex Tetreault @ Boris Lekumovich on Aug 15, 2016 10:40 AM

Hi,

Thanks so much. That was it. Should have made that connection myself.

Alex

Actions

Ian Staines

@ Alex Tetreault on Sep 14, 2016 3:32 PM

I just wanted to confirm that you were successfully able to remove the account using this syntax? I have a customer reporting that "Add account to group" and "Remover account from group" are not working for them.

Actions

Alex Tetreault @ Ian Staines on Dec 13, 2016 3:38 PM

Hi,

Yes, it worked. Sorry for the lat reply.

Alex

Actions

Ian Staines

@ Alex Tetreault on Dec 13, 2016 3:50 PM

Note that in addition to "Remove account from group", there is a companion verb "Remove User from Group" that is available in 7.0.1 and later Web Services. This fills the requirement for a slightly different use case.

Actions

10 Replies

Boris Lekumovich Sep 12, 2015 2:00 AM
Unmark Correct
Correct Answer
first, you need to send a loginUser, to get the token.
Here is an example:

Send a post request to: http://172.31.xx.xx:8080 /aveksa/command.submit?cmd=loginUser
```
<username>AveksaAdmin</username>
<password>AveksaPassword</password>
```
The response will look like this:
```
token=ws31990ea07fcd1e8896:51aa757c:14f368f147f:-71450.08224484800695109
```
Now, you can send your createChangeRequest to:
http://172.31.240.178:8080/aveksa/command.submit?cmd=createChangeRequest&token=ws31990ea07fcd1e8896:51aa757c:14f368f147f:-71450.08224484800695109

Here is an example to removing entitlement

<Changes>
   <Description>desc</Description>
   <Notes>notes</Notes>
   <AccountChange>
   <Operation>Remove</Operation>
   <Account>testaccount</Account>
   <AccountCollector>Payroll Account Collector</AccountCollector>
   <BusinessSource>Payroll</BusinessSource>
   <Resource>401k</Resource>
   <Action>Administrator</Action>
   </AccountChange>
</Changes>
Like • Show 0 Likes0
Actions
- Lakshman Varadharajan @ Boris Lekumovich on Sep 14, 2015 2:12 PM
  Mark Correct
  Correct Answer
  Thank you BorisL,
  It worked.
  
  Then when i tried for Delete account it is throwing the below error.
  412 The change request could not be created. Changes element could not be found. Query String=cmd=createChangeRequest&token=ws31aeb9bdb40ee71b3a:a877881:14fcccd3d12:-7d320.865717998328923
  
  Below is the payload
  
  <AccountChange>
  <Operation>Delete</Operation>
  <User>user1</User>
  <BusinessSource>IAG Application</BusinessSource>
  </AccountChange>
  
  Any idea why ?
  Like • Show 0 Likes0
  Actions
  - Lakshman Varadharajan @ Lakshman Varadharajan on Sep 14, 2015 2:21 PM
    Mark Correct
    Correct Answer
    I got it..
    we need to send the payload as below
    
    <Changes>
    <AccountChange>
            <Operation>Delete</Operation>
            <Account>user1</Account>
            <AccountCollector>IAG Application Account</AccountCollector>
            <BusinessSource>IAG Application</BusinessSource>
        </AccountChange>
    </Changes>
    
    The documentation is misleading
    Like • Show 0 Likes0
    Actions
- Alex Tetreault @ Boris Lekumovich on Mar 30, 2017 12:02 PM
  Mark Correct
  Correct Answer
  Hi,
  
  We are trying to remove a local entitlement from a user but getting an error about the system not be able to find the user. If we try to remove the AD account for the same user, it works fine.
  
  Here is the XML for removing the local entitlement:
  <Changes>
  <Description>Test</Description>
  <Notes>Removing local entitlement</Notes>
  <UserChange>
  <Operation>Remove</Operation>
  <User>akc1234</User>
  <BusinessSource>Manual Tasks - L1</BusinessSource>
  <Resource>RSA Admin</Resource>
  <Action>RSA - Helpdesk</Action>
  </UserChange>
  </Changes>
  
  This is the error we get:
  The change request could not be created. Could not retrieve user from the id 'akc1234'. <?xml version="1.0"
  encoding="UTF-8"?><UserChange> <Operation>Remove</Operation> <User>akc1234</User> <BusinessSource>Manual Tasks -
  L1</BusinessSource> <Resource>RSA Admin</Resource> <Action>RSA - Helpdesk</Action> </UserChange> Query
  String=cmd=createChangeRequest&token=ws31e08acc70b374b2db:7ba4cdf8:15b1f554598:25d90.5321081583431172
  description A specified precondition has failed for this request (The change request could not be created. Could not retrieve
  user from the id 'akc1234'. <?xml version="1.0" encoding="UTF-8"?><UserChange> <Operation>Remove</Operation>
  <User>akc1234</User> <BusinessSource>Manual Tasks - L1</BusinessSource> <Resource>RSA Admin</Resource> <Action>RSA -
  Helpdesk</Action> </UserChange>
  
  Since we can delete or add accounts and other platform entitlements for the same user, we know the user does exist. I tried removing the entitlement from an account, but there really is no account for a local entitlement.
  
  Thanks,
  Alex
  636-722-7684
  Like • Show 0 Likes0
  Actions
Alex Tetreault Aug 12, 2016 4:09 PM
Mark Correct
Correct Answer
Hi,

In the example provided as the answer to the original question, what is the entitlement? 401k? Administrator? Without using the XML tag in the answer, what goes in the XML tags Resource and Action?

I'm trying to remove an Active Directory group and have tried both the 'Remove entitlement from user' and 'Remove entitlement from account' change request actions with different flavors of Resource and Action, but it keeps responding that 'the entitlement for resource and action can't be found for application. I know the group is there though because I can see it under the 'What Access' tab in the Directory.

It would be really helpful if there was better documentation for using the web services including examples of what the XML tags are mapped to.

Thanks,
Alex
Like • Show 0 Likes0
Actions
- Boris Lekumovich @ Alex Tetreault on Aug 14, 2016 1:59 AM
  Mark Correct
  Correct Answer
  Alex, try using "Remove account from group" capability
  Like • Show 0 Likes0
  Actions
  - Alex Tetreault @ Boris Lekumovich on Aug 15, 2016 10:40 AM
    Mark Correct
    Correct Answer
    Hi,
    Thanks so much. That was it. Should have made that connection myself.
    Alex
    Like • Show 0 Likes0
    Actions
    - Ian Staines @ Alex Tetreault on Sep 14, 2016 3:32 PM
      Mark Correct
      Correct Answer
      I just wanted to confirm that you were successfully able to remove the account using this syntax? I have a customer reporting that "Add account to group" and "Remover account from group" are not working for them.
      Like • Show 0 Likes0
      Actions
      - Alex Tetreault @ Ian Staines on Dec 13, 2016 3:38 PM
        Mark Correct
        Correct Answer
        Hi,
        
        Yes, it worked. Sorry for the lat reply.
        Alex
        Like • Show 0 Likes0
        Actions
        Ian Staines @ Alex Tetreault on Dec 13, 2016 3:50 PM
        Mark Correct
        Correct Answer
        Note that in addition to "Remove account from group", there is a companion verb "Remove User from Group" that is available in 7.0.1 and later Web Services. This fills the requirement for a slightly different use case.
        Like • Show 0 Likes0
        Actions

Aveksa Web Service command CreateChangeRequest

Outcomes

Related Content

Recommended Content