
GouravA.83173 (Customer) asked a question.
I'm trying to update a rule on a sign on policy to switch to persistent cookies. I'm using the postman collection provided by Okta to do so. Retrieving Information through the get requests is working fine, I can see all my policies and rules but when I try to update one of my rules, it sends back 200 status and the policy remains unchanged.

Hi @GouravA.83173 (Customer) ,
Can you share the postman request details (URL, payload and response) ?
Thank you.
I've had a ticket open for this same bug for 6 months. No update yet.
Hey @raj.nadimpalli1.5634849829812683E12 (Okta) I had also submitted a case and I provided the okta request id over the email. But here's a general request response.
Request URL:
<Okta domain url>/api/v1/policies/<policy id>/rules/<rule id>
Body:
{
"name": "Persistent Sessions",
"actions": {
"signon": {
"session": {
"usePersistentCookie": true,
"maxSessionIdleMinutes": 120,
"maxSessionLifetimeMinutes": 0
}
}
},
"type": "SIGN_ON"
}
Part of the Response:
"actions": {
"signon": {
"access": "ALLOW",
"requireFactor": false,
"primaryFactor": "PASSWORD_IDP",
"rememberDeviceByDefault": false,
"session": {
"usePersistentCookie": false,
"maxSessionIdleMinutes": 120,
"maxSessionLifetimeMinutes": 0
}
}
},
This is the exact same attribute I've been trying to update for 6 months and had a ticket open.
Okta support, please see case #01009806
Hey @NateO.69773 (Customer)
This got resolved for me. I was missing 'https' at the beginning of the request that's all. Also the persistent session doesn't work for admins/superadmins on okta. Only for the regular users. Hope this helps!
Wow, thank you for responding! This resolved my issue as well.
Open ticket with Okta for over 6 months :D
Thanks Gourav!!