It is unclear from the API docs if it is possible to activate a user in Okta once they have been deactivated.
I can see that they go to a deprovisioned status when they have been deactivated, and I know that the user will be pulled from any applications (all according to the documentation), but my question isn't answered in the docs.
Could I make an update to set the status of the user to "STAGED" and with an updated Profile object, and then call activate?
In Okta Document I have seen "Deactivating a user is a destructive operation. The user is Deprovisionedfrom from all assigned applications that may destroy their data such as email or files. This action cannot be recovered!"
But I Deactivated the User and the Status was set to Deprovisioned, and by making Activate User Postman call I can set Provisioned Status again.
Here are the Okta Documentations call details to Deactivate and activate the user.
https://developer.okta.com/docs/reference/api/users/#deactivate-user
https://developer.okta.com/docs/reference/api/users/#activate-user
Simply try with postman It will work.
I don't know about the STAGED status, but I do know that you can re-activate a deactivated user.
Below is a GET request on a deactivated user:
{
"id": "00ueq20eKcFJlFzHz355",
"status": "DEPROVISIONED",
"created": "2018-08-01T08:29:38.000Z",
"activated": "2018-08-02T12:02:26.000Z",
"statusChanged": "2018-08-02T12:03:38.000Z",
"lastLogin": null,
"lastUpdated": "2018-08-02T12:03:38.000Z",
"passwordChanged": null,
"profile": {
"firstName": "Jim",
"lastName": "Bean",
"mobilePhone": "083274628237462",
"secondEmail": null,
"login": "jim.bean#test.com",
"email": "jim.bean#test.com"
},
"credentials": {
"provider": {
"type": "OKTA",
"name": "OKTA"
}
},
"_links": {
"activate": {
"href": "https://mydomain.okta.com/api/v1/users/00ueq20eKcFJlFzHz355/lifecycle/activate",
"method": "POST"
},
"self": {
"href": "https://mydomain.okta.com/api/v1/users/00ueq20eKcFJlFzHz355"
},
"delete": {
"href": "https://mydomain.okta.com/api/v1/users/00ueq20eKcFJlFzHz355",
"method": "DELETE"
}
}
}
By sending a POST request to https://mydomain.okta.com/api/v1/users/00ueq20eKcFJlFzHz355/lifecycle/activate you can activate the user.
Related
I'm trying to create new users with Slack SCIM API. I've managed to create a new user without password but the invite email was newer sent. I've send following post to https://api.slack.com/scim/v1/Users
{
"schemas": ["urn:scim:schemas:core:1.0",
"urn:scim:schemas:extension:enterprise:1.0"],
"userName": "samplename",
"nickName": "samplename",
"name": {
"familyName": "sample",
"givenName": "name"
},
displayName": "sample name",
"emails": [
{
"value": "sample.name#gmail.com",
"type": "work",
"primary": true
}
],
"userType": "sample",
"title": "sample",
"active":true
}
I can see the user created in the user list but never got the actual invite. (yes I checked spam). Is there even a way for this user to login?
I have a live facebook app, with proper permissions (verified with Graph API). I can create custom Dashboards with all the relevant data, and I get data in my Event Manager.
Current Permissions (Granted and Declined):
{
"data": [
{
"permission": "user_birthday",
"status": "granted"
},
{
"permission": "user_likes",
"status": "granted"
},
{
"permission": "user_gender",
"status": "granted"
},
{
"permission": "email",
"status": "granted"
},
{
"permission": "public_profile",
"status": "granted"
},
{
"permission": "user_friends",
"status": "declined"
},
{
"permission": "read_insights",
"status": "declined"
}
What I'm having an issue with is with the "Active Users" tab under "Activity". It keeps telling me there isn't enough data, however journeys for the same time period show over 17K journeys, my custom dashboards show similar numbers (19K) for impressions and logins.
What constitutes "Active Users" and why would I not be seeing anything under the Analytics component of the Analytics Explorer?
If there is another post or documentation that clarifies this, or if additional information is required, please let me know.
Thank you in advance
"User Activity" or "Active Users" actually only looks at a few events, which are listed here: https://www.facebook.com/help/analytics/1747887018756757
If you're not logging any of those events, then you won't see any data under "Active Users."
We need help in understanding how Microsoft teams like and dislike works with BotFramework. When user clicks on like option provided in background we are getting reactionID but how do we get to know for which specific message user has given his feedback. Do we have this feasibility on Teams?
You can find it in the replyToId. Example from the docs:
The messageReaction event is sent when a user adds or removes his or her reaction to a message which was originally sent by your bot. replyToId contains the ID of the specific message.
{
"reactionsAdded": [
{
"type": "like"
}
],
"type": "messageReaction",
"timestamp": "2017-10-16T18:45:41.943Z",
"id": "f:9f78d1f3",
"channelId": "msteams",
"serviceUrl": "https://smba.trafficmanager.net/amer-client-ss.msg/",
"from": {
"id": "29:1I9Is_Sx0O-Iy2rQ7Xz1lcaPKlO9eqmBRTBuW6XzkFtcjqxTjPaCMij8BVMdBcL9L_RwWNJyAHFQb0TRzXgyQvA",
"aadObjectId": "c33aafc4-646d-4543-9d4c-abd28e4d2110"
},
"conversation": {
"isGroup": true,
"id": "19:3629591d4b774aa08cb0887902eee7c1#thread.skype"
},
"recipient": {
"id": "28:f5d48856-5b42-41a0-8c3a-c5f944b679b0",
"name": "SongsuggesterLocal"
},
"channelData": {
"channel": {
"id": "19:3629591d4b774aa08cb0887902eee7c1#thread.skype"
},
"team": {
"id": "19:efa9296d959346209fea44151c742e73#thread.skype"
},
"tenant": {
"id": "72f988bf-86f1-41af-91ab-2d7cd011db47"
}
},
"replyToId": "1:19uJ8TZA1cZcms7-2HLOW3pWRF4nSWEoVnRqc0DPa_kY"
}
Note, however, that this replyToId is specific to Teams and I don't believe it will persist if you set it yourself. Once you have that, you can update the activity.
If you're trying to analyze which messages are reacted to, you might want to log the outgoing activity's Id and Text in TurnContext.OnSendActivities. Then, when a reaction comes in, you can use the new Activity Handler to handle the message and add the reaction to your log. I believe this would come in OnUnrecognizedActivityTypeAsync. This is similar to the previous link, update the activity.
I am trying to save this very simple fhir patient bundle against https://vonk.fire.ly/Bundle, by doing a PUT using Postman, however I am not able to get it working. When I simply copy the inner Patient resource data and do a PUT directly to the https://vonk.fire.ly/Patient endpoint it works just fine (for example - I just did it to this url https://vonk.fire.ly/Patient/deb7338181).
Can someone please please point me in the direction of what exactly it is going wrong here in this bundle??
{
"resourceType": "Bundle",
"id": "b6ec685a-26a2-4bb3-814b-841fba6a6edb",
"meta": {
"lastUpdated": "2018-05-29T23:45:32Z"
}
"type": "transaction",
"entry": [
{
"resource": {
"resourceType": "Patient",
"id": "deb73381811",
"text": {
"status": "generated",
"div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">Some narrative</div>"
},
"active": true,
"name": [
{
"use": "official",
"family": "Chalmers1",
"given": [
"Peter1",
"James1"
]
}
],
"gender": "male",
"birthDate": "1974-12-25"
},
"request": {
"method": "POST",
"url": "Patient"
}
}
]
}
If you want to send a transaction to a FHIR server, you do a POST of the transaction Bundle to the endpoint, just like you mention in your comment. Within the transaction, for each entry you have to set the request part to the kind of request you want.
For your Patient entry you have asked the server to do a POST, which means a create with a server assigned ID. If you want the server to use your own ID, you should instruct it to perform a PUT, which is usually an update, but can also be used for create with your own ID.
The syntax for the update request is:
"request": {
"method": "PUT",
"url": "Patient/<my_patient_id>"
}
Please note that although it is a valid FHIR request and Vonk allows it, not all servers will.
Trying to create invitations using their API, I get a proper result back, however the status is "notsent". There is zero debug information to go by, so I'm wondering if anyone else has seen this and might have ideas for fixing the issue.
Here's an example of a response I got from their api:
{
"businessUnitId": "<business unit id here>",
"businessUserId": "<business user id here>",
"createdTime": "2018-10-02T09:58:35.135569Z",
"id": "<invitation id here>",
"locale": "da-DK",
"preferredSendTime": "2018-10-09T09:58:34Z",
"recipient": {
"email": "<email goes here>",
"name": "<name goes here>"
},
"redirectUri": "http://trustpilot.com",
"referenceId": "<our ref id>",
"replyTo": "trustpilot#boozt.com",
"sender": {
"email": "noreply.invitations#trustpilotmail.com",
"name": "Booztlet.com"
},
"sentTime": null,
"source": "InvitationApi",
"status": "notsent",
"tags": [],
"templateId": "57cfc1a660e1cc0620b53a38"
}
So, the NotSent status code is expected for new invitations. This is because invitations are sent asynchronously - at around the time you put in as your "preferredSendTime".
If you login to your account at https://businessapp.b2b.trustpilot.com/#/invitations/invitation-history, you should be able to see the invitation you created, and whether it was sent or not (since you specified October 9th as your preferredSendTime, the invitation will still be queued until that point)