Timeline for Setting up a custom idp for AWS SFTP using Active Directory
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 9, 2019 at 16:39 | vote | accept | AddGarbanzos | ||
| Oct 9, 2019 at 16:39 | comment | added | AddGarbanzos | Thanks for the extra help! I actually figured out the issue. AWS SFTP username constraints apply whether you are using the managed idp or a custom idp... which don't allow periods. Our default AD names are "first.last". Once I changed the test user to "first-last" it worked fine. Determining if that will be a blocker or not is a different matter altogether. I'll mark this as solved! | |
| Oct 6, 2019 at 16:57 | comment | added | Volodymyr Rudyi | Do you mean the SFTP event for the AWS Lambda? Try logging the event/request in the AWS Lambda and check the result in CloudWatch. As for the issue with the AD Connector, it's very setup-specific, so it will require analyzing your setup... | |
| Oct 4, 2019 at 23:41 | comment | added | AddGarbanzos | So I got your version with Simple AD up and running in a test instance, but I'm having issues getting it to talk properly with our setup. We have an AD Connector set up in Directory Services. Currently trying to figure out how to configure a test event for the lambda function, but am not entirely sure the syntax to use. Would you have any ideas on how to approach this? | |
| Oct 1, 2019 at 19:50 | comment | added | AddGarbanzos | That looks perfect! Thank you so much. Your guys' blogs have been a huge help in sorting this stuff out. Going to test it out this solution this afternoon. | |
| Sep 29, 2019 at 11:25 | review | First posts | |||
| Sep 29, 2019 at 16:20 | |||||
| Sep 29, 2019 at 11:23 | history | answered | Volodymyr Rudyi | CC BY-SA 4.0 |