-
Suggestion
-
Resolution: Unresolved
-
None
-
44
-
Problem Definition
- The UI doesn't show any steps or tips on how to create a CSV that works with the "Bulk entry" feature in authentication policies
- The error message shown is generic
Suggested Solution
- Add some text in the UI or link to documentation to instruct customers on how to best format CSVs for bulk entry
- More descriptive error message showing what the error is and at which line the error occurs
Why this is important
- The feature is not very forgiving with various CSV formats, formatting and encoding, e.g.
ACCESS-1063 - Successful validation/passing can be quite frustrating as it requires some trial and error - especially when the error message is not descriptive
- Many customers prefer Excel for CSV editing/creation - CSVs generated by Excel has many potential quirks which may cause issues with the bulk entry feature due to the many formatting options/features offered in Excel
Workaround
- Use a text editor to visually validate the CSV and ensure that there aren't any unexpected characters or spacing. Expected formatting:
email1@domain.com,email2@domain.com,email3@domain.com,email4@domain.com,email5@domain.com
OR
email1@domain.com, email2@domain.com, email3@domain.com, email4@domain.com, email5@domain.com
- Applications or OSs may unexpectedly add random characters to the CSV
- If exporting the CSV from another authentication policy, be sure to remove any headers or other non-email columns from the CSV.
- duplicates
-
ACCESS-1085 Provide more details about why an Authentication Policy CSV import failed and the accounts that caused it
- Closed
[ACCESS-1082] Authentication policies: Add bulk entry option CSV formatting instructions and more descriptive error messages
Description |
Original:
h3. Problem Definition
* The UI doesn't show any steps or tips on how to create a CSV that works with the "Bulk entry" feature in authentication policies * The error message shown is generic h3. Suggested Solution * Add some text in the UI or link to documentation to instruct customers on how to best format CSVs for bulk entry * More descriptive error message showing what the error is and at which line the error occurs h3. Why this is important * The feature is not very forgiving with various CSV formats, formatting and encoding, e.g. * Successful validation/passing can be quite frustrating as it requires some trial and error - especially when the error message is not descriptive * Many customers prefer Excel for CSV editing/creation - CSVs generated by Excel has many potential quirks which may cause issues with the bulk entry feature due to the many formatting options/features offered in Excel h3. Workaround * Use a text editor to visually validate the CSV and ensure that there aren't any unexpected characters or spacing. Expected formatting: {noformat} email1@domain.com,email2@domain.com,email3@domain.com,email4@domain.com,email5@domain.com {noformat} *OR* {noformat} email1@domain.com, email2@domain.com, email3@domain.com, email4@domain.com, email5@domain.com {noformat} * Applications or OSs may unexpectedly add random characters to the CSV |
New:
h3. Problem Definition
* The UI doesn't show any steps or tips on how to create a CSV that works with the "Bulk entry" feature in authentication policies * The error message shown is generic h3. Suggested Solution * Add some text in the UI or link to documentation to instruct customers on how to best format CSVs for bulk entry * More descriptive error message showing what the error is and at which line the error occurs h3. Why this is important * The feature is not very forgiving with various CSV formats, formatting and encoding, e.g. * Successful validation/passing can be quite frustrating as it requires some trial and error - especially when the error message is not descriptive * Many customers prefer Excel for CSV editing/creation - CSVs generated by Excel has many potential quirks which may cause issues with the bulk entry feature due to the many formatting options/features offered in Excel h3. Workaround * Use a text editor to visually validate the CSV and ensure that there aren't any unexpected characters or spacing. Expected formatting: {noformat} email1@domain.com,email2@domain.com,email3@domain.com,email4@domain.com,email5@domain.com {noformat} *OR* {noformat} email1@domain.com, email2@domain.com, email3@domain.com, email4@domain.com, email5@domain.com {noformat} * Applications or OSs may unexpectedly add random characters to the CSV * If exporting the CSV from another authentication policy, be sure to remove any headers or other non-email columns from the CSV. |
Support reference count | Original: 43 | New: 44 |
Support reference count | Original: 42 | New: 43 |
Support reference count | Original: 41 | New: 42 |
Support reference count | Original: 40 | New: 41 |
Support reference count | Original: 39 | New: 40 |
Support reference count | Original: 38 | New: 39 |
Assignee | Original: Fabio Hsu [ 34501a0803d4 ] |
Assignee | Original: Matthew Ho [ maho ] | New: Fabio Hsu [ 34501a0803d4 ] |
Support reference count | Original: 37 | New: 38 |