Unable to view SDC GUI from ONAP portal

 
1
0
-1

I have deployed the ONAP portal in machine1 and deployed the SDC module containers in machine2. And updated the correct IP address and DNS in /etc/hosts file. Also I have created a consumer in SDC. Then when I tried to access SDC GUI from ONAP portal, I am getting the following issue: 

HTTP ERROR 305

Problem accessing /sdc1/portal. 
Reason: Missing headers in request

    CommentAdd your comment...

    3 answers

    1.  
      1
      0
      -1

      for reference and debugging SDC please use this:SDC Troubleshooting

        CommentAdd your comment...
      1.  
        1
        0
        -1

        I have fixed this issue.
        Root cause of this issue, the portal App and SDC have different decryption keys (API uses this key to decrypt the login credentials).

        Fix: I have copied the value of decyrption_key property available inside the system.properties and pasted it as a value of the decryption_key property available in the AUTO.json (available in SDC machine). And restarted all the SDC containers. 
        Now I am able to access the SDC GUI

        1. Suryansh Pratap

          Hi, 

          The decryption key is same for me, still I am getting error 305, headers missing.

          Can you please help.

        2. Michael Lando

          what version of sdc are you using that you see thsi issue?

        3. Suryansh Pratap

          Deploying ONAP by OOM as per Beijing release, follwing are the versions:

          sdc-2.0.0

          sdc-fe : image: onap/sdc-frontend:1.2.0

          sdc-be : image: onap/sdc-backend:1.2.0

          PFB details for the error message:

          HTTP ERROR 305

          Problem accessing /sdc1/portal. Reason:

              Missing Headers In Request


          Powered by Jetty:// 9.3.23.v20180228

        4. Ryan LIU

          I have the same decryption_key but it still reports "Missing Headers In Request"

          bash-4.4# grep decryption ./root/chef-solo/environments/AUTO.json

                      "decryption_key": "= AGLDdG4D04BKm2IxIWEr8o=="

          bash-4.4#

           grep decryption ./opt/apache-tomcat-8.0.37/webapps/ONAPPORTAL/WEB-INF/conf/system.properties

          decryption_key                            = AGLDdG4D04BKm2IxIWEr8o==

          / #

          nexus3.onap.org:10001/onap/sdc-frontend                                            1.2.0

          nexus3.onap.org:10001/onap/portal-app                                              2.2.0 


          Could you please help on it?

        5. Suryansh Pratap

          Please use FQDN everywhere like:

          http://portal.api.simpledemo.onap.org:8989/ONAPPORTAL/login.htm

          Host file configuration:

          10.12.6.155 portal.api.simpledemo.onap.org
10.12.6.155 sdc.api.fe.simpledemo.onap.org

          Add one more line in your hosts file:

          10.12.6.155 sdc.fe.simpledemo.onap.org


          Please let me know if still you are facing the error.

          Thanks


        6. Ryan LIU

          Suryansh Pratap thanks a lot for your support. you are right. I tried to use fqdn yesterday. it really works. one question is why IP does not work?

          And when I do "Manage" → "Design" → "Create a Product" or "Create a Vendor..". both output GUI is same with "User Management" and "Catagory Management". Is there something wrong?

          And Click "SDC" from "Home" nothing show up. IS there any configuration error?

          Thanks,

          Ryan

        7. Suryansh Pratap

          Hi, Sorry i do not have any idea about that. If i get to know anything, I will update you & please do vice-versa if possible.

          Thanks

        8. Ryan LIU

          @Suryansh Pratap, thanks for your response. do you know who can help on this area?


          Thanks,

          Ryan

        9. Ryan LIU

          Fix this issue. it is because I logged in as demo which only has admin role w/o designer role. after I logged in as cs0008 which has designer role then I can access sdc UI.


          Thanks for your support.

          Ryan

        CommentAdd your comment...
      2.  
        1
        0
        -1

        It may be the sdc didn't start up normally.

        docker logs -f XXXX

        To see the log of the docker containers. Reinstall sdc if necessary.

          CommentAdd your comment...