Posted  by  admin

Okta Slack

  1. Zoom Okta
  2. Okta Slack Integration

New to Okta and new to Slack integrations as well, but I had/have a similar question. Recently began managing a system with 21 similar errors to the original posting. Are the 'usernames' unique to the enterprise instance, or slack itself? Meaning, can I have a 'john.doe' for XYZ Company and a 'john.doe' for ACME Company? If you added the Slack app previously, on the OktaAdmin Console click Applications and select Slack in the list of applications. Click the Provisioning tab, click Configure API Integration, and select the Enable API Integration check box. Click Authenticate with Slack. The Slack application opens in a new window.

Between COVID-19, overdue conversations around racial injustice, and businesses transitioning to distributed work, this year has presented us with multiple crises, but also opportunities for change.

Navigating through these crises towards a “new normal” demands steady leadership. Technology leaders today find themselves sharing responsibility for safeguarding the well-being of employees and their loved ones, while redefining their role in marshaling resources that help customers thrive in this evolving business environment.

That’s why Okta co-hosted a unique event last week, moderated by Bloomberg‘s Emily Chang. Okta’s CEO Todd McKinnon joined Eric Yuan, CEO & Co-Founder of Zoom, Stewart Butterfield, CEO & Co-Founder of Slack, and Aaron Levie, CEO, Co-Founder & Chairman of Box, in an exclusive virtual event. These executives discussed how companies can drive meaningful leadership in difficult times across their ecosystems, to impact employees, customers, and partners.

This wasn’t a “present your slides” kind of event. It was a frank, moderated, open conversation among Todd, Eric, Stewart, and Aaron who, over the last few years, have become friends, colleagues, and strategic collaborators. They don’t agree on everything, which made for a lively conversation where they each shared hands-on guidance directed towards helping CEOs and CxOs lead through this crisis.

In this post, I summarize the top four themes from the event. (For the entire talk, watch “Leadership through crisis: Perspectives as we create our new normal”, right here.)

1. Be grateful, show up more, engage proactively

Emily asked what it’s like being a CEO in this moment. The panel agreed, these are trying times for all, with particular acknowledgment of the challenges of front-line responders around COVID-19, and all those impacted economically. They expressed their gratitude for the health of their employees and loved ones. The panelists also agreed that the technology industry hasn’t been as hard-hit as others, as our jobs can be easily and safely practiced in remote environments. But the upheaval has also forced change in how they think about their roles as leaders.

Single

“With shelter in place, I amped up my visibility and activity on social media to communicate more, and proactively, with our employees and customers.”

Okta

—Todd McKinnon, CEO, Okta

Todd mentioned that, as the CEO of Okta for 11 years, he previously did not have to make decisions that would impact the basic health of his employees. Each of the panelists agreed that they’ve found counsel and support from each other–as well as other technology leaders–invaluable during these times.

2. Deliver user happiness, optimize time better, allow WFH flexibility

As the CEOs exchanged stories, some patterns of change became abundantly clear. In this “new normal,” companies are hiring people without ever meeting them in person; sales teams are closing deals without the typical in-person workshops with clients, and marketing teams are evolving from in-person events to physical ones.

Okta slack app

With a relentless focus on best-of-breed experiences at Okta, Zoom, Slack, and Box, we enable organizations to work remotely while being productive. For example, at Zoom, Eric’s teams are building more connections with users. Zoom is working on ways to enhance user experience, like providing controls for lightening the background or retouching your “quarantine face,” or optimizing noise reduction when you are secretly eating during a call.

“We do all we can to truly deliver happiness to our users, even under pressure.”

Fox

—Eric Yuan, CEO, Zoom

Distributed teams are also finding that they can optimize work differently with remote work. An example Stewart shared is that Slack’s traditional “all-hands” team meetings used to be carefully choreographed affairs. Since quarantine, they have become informal, 20-minute-long, content-only sessions, and employees appreciate the candor. It’s an improvement that might never have happened if quarantine hadn’t forced it on them. Similarly, teams used to have to weigh the opportunity cost of traveling out to meet an important client. Now, they can optimize the day differently: be on a video with one customer, then another, then spend an hour doing crucial home tasks. This new kind of flexibility is fundamental and valuable.

3. Dynamic Work is here to stay, so embrace it

The panelists agreed that decades of old practices of what constitutes “work” have been challenged—in a very short span of time. They discussed that before COVID-19, big decisions were made by whichever stakeholders could fit in your conference room.

Now we’re forced to reconsider that, and it’s a unique opportunity. We can easily support Dynamic Work that ignores the old restrictions of physical space by using a 100-person Slack channel or a 30-person Zoom call where everyone can contribute ideas. And because we can, we must.

“Now, teams are not limited by the people that they sit by to get the best ideas flowing. We can engage our entire workforce in our company-wide interactions virtually; we can easily reach and connect with more customers over video; and more voices, at all levels of the organization, can be heard in every meeting. By leveraging a modern tech stack with best-of-breed technologies allows teams to easily and securely work from anywhere.”

—Aaron Levie, CEO and cofounder, Box

“The holy grail we've all talked about for years is here” said Aaron. He spoke about re-looking at concepts like resilience, not just from a view of high performing individuals, but across teams that collaborate differently to drive innovations.

4. Remember your north star, then take a conscious stand

The panelists also agreed that this is a time of global reckoning with broad repercussions for years to come. But through it all, leaders have an opportunity to resist the comfort of reverting to old habits and ask what their companies really stand for.

“Everyone's been in such a scramble just to continue operations in this new environment — but what do we want to change?”

—Stewart Butterfield, CEO, Slack

Stewart also pointed out how the boundaries of discussions have shifted positively on fundamental human rights issues. All the leaders agreed that not taking a stand is not an option for CEOs in this new world, but that a stand must be taken, consciously and consistently.

Final thoughts on tackling the future

We can’t predict exactly what the outcome of this ever changing landscape will be, but we’re excited to partner with Zoom, Slack, Box, and countless other organizations to support the new future of work. We’re all striving for a future that supports distributed work, and enables businesses to be strong and resilient. This panel discussion was a rare opportunity for our company CEOs and teams to come together to share best practices. We’re hoping it can help every leader and changemaker interested in shaping a positive new normal in the 2020s.

If you missed the webinar or want a refresher, take a look at the Leadership through crisis: Perspectives as we create our new normalrecording.

Okta lambda school

Zoom Okta

Sections:

Okta Slack Integration

  • Introduction

    This walk-through demonstrates how to use Workflows to onboard contractors using time-based actions. We’ll create a user in Okta in a Staged status, and then activate their account on their start date. Later, we’ll automatically suspend their account after a designated time.

    Familiarize yourself with the Workflows basics:

    Prerequisites:

    • Okta and Slack connections
    • Postman
    • Custom attributes in your Okta profile (see below)

    Add custom attributes

    1. In Admin Console, go to Directory > Profile Editor.
    2. Select your Okta profile, and then click Edit.
    3. In Profile Editor, click Add Attribute.
      • In the Data type field, select boolean.
      • In the Display Name field, enter contractor.
      • In the Variable name field, enter contractor.
      • Click Save and Add Another.
      • Leave Data type set to _string.
      • In the Display Name field, enter Activation Date.
      • In the Variable name field, enter activationDate.
    4. Click Save.
  • Create a table

    1. In Admin Console, go to Workflow > Workflows console.
    2. In the Tables tab, click Create a Table Now.
    3. Name your table Contractor Access, and then click Save.
    4. Click New Column, and name your column userID.
    5. Click Add Another, and then create the following columns:
      • displayName
      • userName
      • oktaCreateDate (change this field type to Date)
      • activateDate (change this field type to Date)
      • suspendDate (change this field type to Date)
      • status
      • Click Create.
  • Build a user creation Flow

    1. In the Flows tab, click Create a Flow Now.
    2. Name your Flow 1) User Created in Okta, and select Save All Data. Click Save.
    3. Click Add Event, and then select Okta from the menu of applications.
    4. In the Okta Events menu, select User Created.
    5. Click Add Action, and then select Okta from the menu of applications.
    6. In the Okta Actions menu, select Read User.
    7. In the Attributes list, select Username, First name, Last name, contractor, and Activation Date. Click Done.
    8. Drag and drop the Okta User ID from the User Created card to the ID or Login field of the Read User card.
    9. Click Add Another > Function > Branching > Continue If.
    10. In the Continue If card, change the value a and value b field types to T/F.
    11. Drag and drop the contractor field from the Read User card to the value a field of the Continue If card.
    12. In the Continue If card, set the comparison field to True.
    13. In the Continue If card, enter the following in the message field: User is not a contractor.
    14. Save the Flow.
  • Calculate term dates

    1. In the same Flow, click Add Another > Function > Date and Time > Add.
    2. Drag and drop the Activation Date field from the Read User card to the Start Date field on the Add card.
    3. In the Add card, enter 30 into the Add field.
    4. In the Unit field, select Days.
    5. Click the Edit icon on the Add Card, and then select Edit Card.
    6. Change the output field to suspendDate, and then click Done.
    7. Save the Flow.
  • Create a row in the table

    1. In the same Flow, click Add Another > Function > Tables > Create Row.
    2. In the Create Row card, click Choose Table, and then select your Contractor Access table.
    3. Select all fields in your table, and then click Done.
    4. Drag and drop the Okta User ID from the User Created card to the userID field in the Create Row card.
    5. Drag and drop the Okta Display Name from the User Created card to the displayName field in the Create Row card.
    6. Drag and drop the username from the Read User card to the userName field in the Create Row card.
    7. Drag and drop the Date and Time from the User Created card to the userCreateDate field in the Create Row card.
    8. Drag and drop the Activation Date from the User Created card to the activationDate field in the Create Row card.
    9. Drag and drop the suspendDate from the Add card to the suspendDate field in the Create Row card.
    10. Drag and drop the Status from the Read User card to the status field in the Create Row card.
    11. Save the Flow.
  • Send a Slack message

    1. In the same Flow, click Add Another > Function > Text > Compose.
    2. In the Compose card, enter the following message: *New contractor added to Okta*.
    3. Drag and drop the displayName from the User Created card to the Compose card.
    4. Drag and drop the userName from the Read User card to the Compose card. Put this attribute in parentheses.
    5. Enter Activation Date: and Suspend Date: in the Compose card.
    6. Drag and drop the Activation Date from the Read User card to the Compose card.
    7. Drag and drop the Suspend Date from the Add card to the Compose card.
    8. Click Add Another > Action.
    9. Select Slack from the list of applications, and then select Send Message to Channel. (You may be prompted to choose your Slack connection).
    10. Select the channel you want to send the message. Our selected channel is contractor_onboarding.
    11. Select Yes to send the message as a bot, and then click Done.
    12. Select all Inputs and Outputs, and then click Done.
    13. Drag and drop the output from the Compose card to the Text field in the Send Message to Channel card.
    14. In the Name field, enter Onboarding Bot.
    15. Save the Flow.
  • Build a Flow to activate users

    1. In Workflows console, click New Flow.
    2. Name your Flow 1) Activate User on Activation Date, and then click Save.
    3. Click Add Event, and then select Schedule from the Okta apps.
    4. In the Flow Schedule window, set the Frequency to daily at midnight, and then click Save.
    5. Click Add Function > Table > Search Rows.
    6. In the Search Rows card, click Choose Table, and then select your Contractor Access table.
    7. In the Result Set field, choose All matching rows.
    8. Click Done, and then be sure that all attributes are selected. Click Done.
    9. Click Filter, and then set the first condition to status with a value of STAGED.
    10. Click Add Another, and set the condition to activation date <=.
    11. Drag and drop the Current Time field from the Scheduled Flow card to the activation date value field.
    12. Click Done.
    13. Click Add Another > Function > List > For Each.
    14. Drag and drop the Rows field from the Search Rows card to the For each item in this list field of the For Each card.
  • Build a child Flow

    1. In the For Each card, click Choose Flow.
    2. Click New Flow.
    3. Name your child Flow 2a) Activate user, and then click Save.
    4. Click Add Event, and then select Child Flow from the Okta Apps.
    5. In the first field, enter contractorRecord. Change the field type to Object.
    6. In the contractorRecord subfields, enter userID, row, Row ID, and suspendDate.
    7. Click Function > Error Handling > If Error.
    8. In the If Error card, select Try.
    9. In the If Error card, click + (Add), and then select Okta.
    10. Choose Activate User.
    11. In the Send Email field, select Yes.
    12. Click Done.
    13. Drag and drop the userID from the Child Flow card to the ID or Login field on the If Error > Try > Activate User card.
    14. In the If Error card, select Error.
    15. In the If Error card, click + Function > Error Handling > Return Error.
    16. Drag and drop the Error from the Error card to the message field of the Return Error card.
    17. Save the child Flow.
  • Send a User Activated Slack message

    1. In your child Flow, click Add Another > App Action.
    2. Select Okta, and then choose Read User.
    3. In addition to the selected attributes, choose Username, First name, and Last name. Click Done.
    4. Drag and drop the userID from the Child Flow card to the ID or Login field on the Read User card.
    5. Click Add Another > Function > Text > Compose.
    6. In the Compose card, enter your message. Drag and drop the values from the other cards where applicable: Contractor [First Name] [Last Name] ([Username]) has been [status]. Their account will be automatically suspended on [suspendDate].
    7. Save the Flow.
    8. Click Add Another > Action.
    9. Select Slack from the list of applications, and then select Send Message to Channel. (You may be prompted to choose your Slack connection.)
    10. Select the channel you want to send the message. Our selected channel is contractor_onboarding.
    11. Select Yes to send the message as a bot, and then click Done.
    12. Select all Inputs and Outputs, and then click Done.
    13. Drag and drop the output from the Compose card to the Text field in the Send Message to Channel card.
    14. In the Name field, enter Onboarding Bot.
  • Update the row in your table

    1. Click Add Another > Function > Tables > Update Row.
    2. In the Update Row card, click Choose Table, and then select your Contractor Access table.
    3. Click Done.
    4. In the attributes list, select status, and then click Done.
    5. Drag and drop the Row ID from the Child Flow card to the Row ID field of the Update Row card.
    6. Drag and drop the Status from the Read User card to the Status field of the Update Row card.
    7. Save the Flow.
  • Trigger the Flow with Postman

    1. Create a test user in Postman with the following attributes:
      • firstName
      • lastName
      • Email
      • Login
      • Contractor (true)
      • activationDate
    2. Click Send.
    3. Verify that the Onboarding Bot sends you an activation message on Slack.
  • Video Walkthrough