terraform-provider-okta: Unable to set App Logo for SAML apps
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave “+1” or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Terraform Version
Terraform v0.14.10 Okta Provider built from https://github.com/okta/terraform-provider-okta/commit/56e5b6be7bfcd6a1ad54e9b8644664b4635e8403
Affected Resource(s)
- okta_app_saml
Terraform Configuration Files
resource "okta_app_saml" "this" {
label = var.label
sso_url = "https://${var.fqdn}/saml2_auth/acs/"
recipient = "https://${var.fqdn}/saml2_auth/acs/"
destination = "https://${var.fqdn}/saml2_auth/acs/"
audience = "https://${var.fqdn}/saml2_auth/acs/"
subject_name_id_template = "$${user.userName}"
subject_name_id_format = "urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress"
response_signed = true
assertion_signed = true
signature_algorithm = "RSA_SHA256"
digest_algorithm = "SHA256"
honor_force_authn = true
authn_context_class_ref = "urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport"
logo = var.logo_filename
hide_web = false
Debug Output
{
"errorCode": "App instance has no login link to set logo for",
"errorSummary": null,
"errorLink": "App instance has no login link to set logo for",
"errorId": "oaelxekIJNkQF6DVVUzjyORsQ",
"errorCauses": []
}
Expected Behavior
App logo should have been uploaded and created
Actual Behavior
Error due to missing App login link which doesn’t appear to be configurable.
Steps to Reproduce
terraform apply
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 15
- Comments: 29 (17 by maintainers)
UPDATE: @fatbasstard @joshowen @virgofx @miguelpuiggarcia @sklarsa @guillaumelecerf @ReeceWilliams7 @gavinbunney
The feature team responsible for the endpoint where app logos are uploaded to has fixed this bug. However, the fix won’t be released to production until mid-November given the way releases are proved and promoted within Okta.
@miguelpuiggarcia I’ve pinged the feature team responsible for this part of the Okta API and am trying to get it into an upcoming sprint.
@guillaumelecerf @sklarsa I’m looking to see when this will be prioritized by the corresponding internal feature team. I will post an update when I find out new information.
The feature team responsible for that Okta API endpoint is now looking for a fix in its current sprint.
@joshowen @gavinbunney there is a known bug where the application icon is able to be updated in the Okta UI but not via the API. It is on the backlog of the responsible team. I will monitor the issue on our end and provide updates here.
Internal reference: OKTA-373430
Sweet, can confirm it works here too now! 🎉
Another “manual” action removed, long live automation!
@fatbasstard yes, this issue will stay open until it’s resolved.
@fatbasstard the bug is still on the responsible team’s backlog but has not been triaged yet. I’ll reference this discussion to illustrate importance.
This also happens for OIDC apps as well 😦 Only bookmark apps I’ve managed to successfully create from scratch and set a logo.
Hi @bogdanprodan-okta - funnily enough I tested this on our preview instance yesterday and meant to update on here. Pleased to report it worked. Thanks for your help (and @monde) in getting this prioritised on your side - much appreciated!
@fatbasstard @joshowen @virgofx @miguelpuiggarcia @sklarsa @guillaumelecerf @ReeceWilliams7 @gavinbunney I’ve tested logo on two different
*.oktapreview.comorgs and it worked! Could you please try to set logos in your orgs?@fatbasstard I’m using our internal process to escalate the issue with the responsible feature team.
Hi, @joshowen @gavinbunney The error you are getting in the response is from the Okta API itself, not the terraform itself. I’m not sure what is the root cause of this bug, but I’ll ask the team responsible for this functionality.