Enhancement: ISC Sources Configuration Page updates in June

Announcements Product News
,
1

Description

:bangbang: Three Sources Configuration Pages will update in June

SailPoint is updating three Sources configuration pages.

Who is affected?

  • All ISC customer customers.
  • Users who are Admin and Source Admins.

Action Required

Learn about the upcoming changes (video below). Validate any impact to your documentation or testing.

Important Dates

06/10/24 (staging)
06/24/24 - 06/28/24 (full rollout)

What is the solution?

  • Three new pages using the new IDN UI with all configuration options previously available.
  • A re-direct button on each of the three “old” Sources config pages.
  • Closing the new Sources config page using the X will return user to the existing Sources config page.

Additional Resources & FAQ

FAQ

Q: Why are you updating these pages?
A: We are aligning to the new ISC UI.

Q: When is the new feature in sandbox?
A: June 10

Q: When is the feature in production?
A: June 24 to June 28

18 Likes
2

This change to the create account page makes a lot of sense.

2 Likes
3

The demo video gives good insight on the change. Thank you for sharing.

1 Like
4

Makes way more sense when setting up a Source. However, some UAT critiques based on the video :

  • the UI elements should be slimmed down
  • The correlation Page Input Field labels BOTH say “Identity Attribute”, instead of the right-sided one saying “Account Attribute”
  • The account Schema page is populated only with “<Row Label>” - this is a more glaring issue, so y’all probably already know about it.
1 Like
5

Good catch - I watched this a few times and did not notice the “Identity”. Thank you for taking the time and providing feedback Vipinjeet!

2 Likes
6

Happy to help!

from Imgflip Meme Generator

4 Likes
7

I am just today seeing this change live in our sandbox. I was in the middle of testing when it changed, and now I cannot edit anything anymore. I cannot click on the new Account Schema location, its greyed out. and clicking the old just invites me to redirect. Sigh :frowning:

1 Like
8

Hi
The Account Schema, Correlation and Create Account screens are greyed out on the source configuration page when the test connection fails.
This was not the case before. We were able to see and edit these pages.
This is a bad design.
For some of our sources, the application Owners want to give lower level of privileges and the SailPoint test connection fails. We ignore these errors as our use cases do not need the full permissions.
We were able to edit the account schema and the correlation pages and our use cases were working.
Now, the Account schema and the correlation pages are not editable.
This is not acceptable.

The Dependency between test connection and the new screens in the source configuration should be removed,

Thanks.

9

Why was the Entitlement schema not moved as well?
Now we still need to go between ‘old’ and ‘new’ pages if we want to define entitlement types.
Is it planned to be included?

1 Like
10

I’m looking at it in sandbox and the “create account (provisioning policy)” does not work, when you put “save”, it stays in “loading” forever. And if you want to create the provisioning policy by API, the source is totally broken and any operation returns a 401 (internal, not from the endpoint). This happens for Web Service and SCIM 2.0 Connectors.

Do you know if you will be able to solve it quickly?

11

Hi @tysremi - The plan is to migrate all sources config pages, but we did not want to slow down the release.

1 Like
12

Hi @jsostaric - we are looking into this. Thank you for bringing it to us!

13

Hi @ranga_vinjamuri and @JessAscanio1

It sounds like you have two users configuring sources. This means one (the user with credentials) may now block the other user performing the “deeper” configuration.

@JessAscanio1 I might be oversimplifying but felt that you hit the ‘blocked’ part.

Some source config screens do requires a connection. For example, CIEM Cloud Sources must successfully connect to retrieve “scopes”. Others connectors do not and I hear that requiring Test connection success is unnecessary. The potential downside would be lots of unconnectible sources with abandoned configuration/correlation.

I will meet with our UX and potentially remove the need to pass a Test connection.
We know we do not want to slow down source configuration and that is probably the simplest path!

14

Great, thanks for the feedback!

15

Great. Thanks Colin.
If the fix can be completed before June 24th, that would be fantastic.

Ranga

16

This fix should be in sandbox @ranga_vinjamuri .

17

Awesome. Thanks Colin!
I see the AI Onboarding for Apps as well!

Ranga Vinjamuri